Method and apparatus for measuring and reporting channel state in wireless communication system

ABSTRACT

The disclosure relates to a communication method and system for converging a 5G communication system for supporting higher data rates beyond a 4G system with a technology for IoT. The disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The disclosure provides a method performed by a terminal in a wireless communication system. The method includes receiving, from a base station, information configuring a list of aperiodic trigger states for CSI; receiving, from the base station, DCI including a CSI request field, wherein each codepoint of the CSI request field is associated with one trigger state of the list and a CSI-RS is triggered based on a trigger state indicated by the CSI request field; identifying whether a BWP in which the CSI-RS is received is non-active; and in case that the BWP in which the CSI-RS is received is non-active, skipping a measurement of the CSI-RS.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. Ser. No. 16/834,357, whichwas filed in the U.S. Patent and Trademark Office on Mar. 30, 2020, andclaims priority under 35 U.S.C. § 119 to Korean Patent Application No.10-2019-0037332, filed on Mar. 29, 2019, in the Korean IntellectualProperty Office, the entire disclosure of each of which is incorporatedherein by reference.

BACKGROUND 1. Field

The disclosure relates generally to a method and an apparatus formeasuring and reporting a channel state in a wireless communicationsystem.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems, efforts have been made todevelop an improved 5G or pre-5G communication system. Therefore, the 5Gor pre-5G communication system is also called a ‘Beyond 4G Network’ or a‘Post LTE System’. The 5G communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, soas to accomplish higher data rates. To decrease propagation loss of theradio waves and increase the transmission distance, the beamforming,massive multiple-input multiple-output (MIMO), Full Dimensional MIMO(FD-MIMO), array antenna, an analog beam forming, large scale antennatechniques are discussed in 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud Radio Access Networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,Coordinated Multi-Points (CoMP), reception-end interference cancellationand the like. In the 5G system, Hybrid FSK and QAM Modulation (FQAM) andsliding window superposition coding (SWSC) as an advanced codingmodulation (ACM), and filter bank multi carrier (FBMC), non-orthogonalmultiple access (NOMA), and sparse code multiple access (SCMA) as anadvanced access technology have been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof Things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofEverything (IoE), which is a combination of the IoT technology and theBig Data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “Security technology” have been demanded forIoT implementation, a sensor network, a Machine-to-Machine (M2M)communication, Machine Type Communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing Information Technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, Machine Type Communication (MTC), andMachine-to-Machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RadioAccess Network (RAN) as the above-described Big Data processingtechnology may also be considered to be as an example of convergencebetween the 5G technology and the IoT technology.

Application of a cloud RAN as the above-described big data processingtechnology may also be considered an example of convergence of the 5Gtechnology with the IoT technology.

In 5G, one or a plurality of bandwidth parts (BWPs) may be configuredfor a terminal, and a bandwidth among the configured BWPs may beactivated. A base station may instruct the terminal to activate aparticular BWP through downlink control information (DCI) indication,and if a BWP index received through DCI is different from the index of aBWP currently activated, the terminal may change the BWP. Sincemeasuring and reporting of a channel state of a newly activated BWP canbe performed after the BWP is activated, the channel state of the newBWP is absent, and it may be difficult to transmit or receive a datachannel immediately after the corresponding BWP is changed.

SUMMARY

The disclosure is made to address at least the disadvantages describedabove and to provide at least the advantages described below.

An aspect of the disclosure is to provide a method and an apparatus for,if an activated BWP is changed in an environment in which a BWP isconfigured and operated, effectively measuring and reporting a channelstate of a changed BWP.

In accordance with an aspect of the disclosure, a method is provided fora terminal in a wireless communication system. The method includesreceiving, from a base station, information configuring a list ofaperiodic trigger states for channel state information (CSI); receiving,from the base station, downlink control information (DCI) including aCSI request field, wherein a codepoint of the CSI request field isassociated with one trigger state of the list, and wherein the onetrigger state comprises at least one CSI report configuration, a CSIreport configuration comprises a CSI resource configuration, and the CSIresource configuration comprises a bandwidth part (BWP) identifier (ID)and in case that a CSI report for a non-active BWP is triggered based onthe CSI request field, a measurement based on a CSI resource in thenon-active BWP is not performed.

In accordance with another aspect of the disclosure, a method isprovided for a base station in a wireless communication system. Themethod includes transmitting, to a terminal, information configuring alist of aperiodic trigger states for channel state information (CSI);and transmitting, to the terminal, downlink control information (DCI)including a CSI request field. A codepoint of the CSI request field isassociated with one trigger state of the list, the one trigger statecomprises at least one CSI report configuration, a CSI reportconfiguration comprises a CSI resource configuration, and the CSIresource configuration comprises a bandwidth part (BWP) identifier (ID).In case that a CSI report for a non-active BWP is triggered based on theCSI request field, a measurement based on a CSI resource in thenon-active BWP is not performed.

In accordance with another aspect of the disclosure, a terminal isprovided for a wireless communication system. The terminal includes atransceiver; and a controller configured to receive, from a basestation, information configuring a list of aperiodic trigger states forchannel state information (CSI), receive, from the base station,downlink control information (DCI) including a CSI request field,wherein a codepoint of the CSI request field is associated with onetrigger state of the list, and wherein the one trigger state comprisesat least one CSI report configuration, a CSI report configurationcomprises a CSI resource configuration, and the CSI resourceconfiguration comprises a bandwidth part (BWP) identifier (ID), and incase that a CSI report for a non-active BWP is triggered based on theCSI request field, a measurement based on a CSI resource in thenon-active BWP is not performed.

In accordance with another aspect of the disclosure provides a basestation is provided for a wireless communication system. The basestation includes a transceiver; and a controller configured to transmit,to a terminal, information configuring a list of aperiodic triggerstates for channel state information (CSI), and transmit, to theterminal, downlink control information (DCI) including a CSI requestfield. A codepoint of the CSI request field is associated with onetrigger state of the list, the one trigger state comprises at least oneCSI report configuration. a CSI report configuration comprises a CSIresource configuration. and the CSI resource configuration comprises abandwidth part (BWP) identifier (ID). In case that a CSI report for anon-active BWP is triggered based on the CSI request field, ameasurement based on a CSI resource in the non-active BWP is notperformed.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of certainembodiments of the disclosure will be more apparent from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a time-frequency domain in 5G according to anembodiment;

FIG. 2 illustrates a frame, subframe, and slot structure in 5G accordingto an embodiment;

FIG. 3 illustrates a BWP configuration in 5G according to an embodiment;

FIG. 4 illustrates a control resource set (CORESET) configuration of adownlink (DL) control channel in 5G according to an embodiment;

FIG. 5 illustrates a basic unit structure for time and frequencyresources of a DL control channel in 5G according to an embodiment;

FIG. 6 illustrates a method of aperiodic CSI measurement and reportingin 5G according to an embodiment;

FIG. 7 illustrates a method of aperiodic CSI measurement and reportingin 5G according to an embodiment;

FIG. 8 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment;

FIG. 9 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment;

FIG. 10 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment;

FIG. 11 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment;

FIG. 12 illustrates a terminal according to an embodiment; and

FIG. 13 illustrates a base station according to an embodiment.

DETAILED DESCRIPTION

Hereinafter, various embodiments of the disclosure will be described indetail with reference to the accompanying drawings. In the followingdescription of embodiments of the disclosure, a 5G system will bedescribed by way of example, but the embodiments of the disclosure maybe applied to other communication systems having similar backgrounds orchannel types. Examples of such communication systems may include theLTE or LTE-advanced (LTE-A) mobile communication system and post-5Gmobile communication technologies to be developed in the future.Therefore, the embodiments of the disclosure may be applied to othercommunication systems through some modifications without significantlydeparting from the scope of the disclosure.

In the following description of the disclosure, a detailed discussion ofknown functions or configurations incorporated herein will be omittedwhen it may make the subject matter of the disclosure unclear. The termswhich will be described below are defined in consideration of thefunctions in the disclosure, and may be different according to users,intentions of the users, or customs. Therefore, the definitions of theterms should be made based on the contents throughout the specification.

For the same reason, in the accompanying drawings, some elements may beexaggerated, omitted, or schematically illustrated. Further, the size ofeach element does not completely reflect the actual size. In thedrawings, identical or corresponding elements are provided withidentical reference numerals.

The advantages and features of the disclosure and ways to achieve themwill be apparent by referring to embodiments as described below indetail in conjunction with the accompanying drawings. However, thedisclosure is not limited to the embodiments set forth below and may beimplemented in various forms. The following embodiments are providedonly to completely disclose the disclosure and inform those skilled inthe art of the scope of the disclosure, and the disclosure is definedonly by the scope of the appended claims. Throughout the specification,the same or like reference numerals designate the same or like elements.

Each block of the flowcharts, and combinations of blocks in theflowcharts, can be implemented by computer program instructions. Thesecomputer program instructions can be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions specified in the flowchart block or blocks.These computer program instructions may also be stored in a computerusable or computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstruction means that implement the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Each block of the flowcharts may represent a module, segment, or portionof code, which includes one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder. For example, two blocks shown in succession may in fact beexecuted substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved.

A “unit” refers to a software element or a hardware element, such as aField Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC), which performs a predetermined function.However, the term “unit” does not mean software or hardware. A “unit”may be constructed either to be stored in an addressable storage mediumor to execute one or more processors. Therefore, the term “unit”includes, for example, software elements, object-oriented softwareelements, class elements or task elements, processes, functions,properties, procedures, sub-routines, segments of a program code,drivers, firmware, micro-codes, circuits, data, database, datastructures, tables, arrays, and parameters. The elements and functionsprovided by the “unit” may be either combined into a smaller number ofelements, or a “unit”, or divided into a larger number of elements, or a“unit”. The elements and “units” or may be implemented to reproduce oneor more central processing units (CPUs) within a device or a securitymultimedia card. Further, a “unit” may include one or more processors.

A base station performs resource allocation to a terminal, and may beone of a gNode B, an eNode B, a Node B, a wireless access unit, a basestation controller, or a node on a network. A terminal may include auser equipment (UE), a mobile station (MS), a cellular phone, asmartphone, a computer, or a multimedia system capable of acommunication function. However, the disclosure is not limited to theexamples above.

In addition, an embodiment will be described based on an example of anew radio (NR) system or an LTE/LTE-A system. However, the embodimentmay be also applied to another communication system having a similartechnical background or channel type. In addition, an embodiment may bealso applied to another communication system through partialmodification without departing from the scope of the disclosure as adetermination of a person who skilled in the art.

Hereinafter, for convenience of explanation, part of terms and namesdefined in 3rd generation partnership project (3GPP) LTE standards willbe used in the disclosure. However, the disclosure is not limited to theterms and names and may be applied to a system following other standardsin the same way.

A wireless communication system has developed to be a broadband wirelesscommunication system that provides a high speed and high quality packetdata service, e.g., using communication standards such as high speedpacket access (HSPA), LTE or evolved universal terrestrial radio access(E-UTRA)), LTE-A, and LTE-Pro of 3GPP, high rate packet data (HRPD), andultra mobile broadband (UMB) of 3GPP2, 802.16e of IEEE, etc., beyond thevoice-based service provided at the initial stages.

An LTE system, which is a representative example of the broadbandwireless communication system, employs an orthogonal frequency divisionmultiplexing (OFDM) scheme for a DL, and employs a single carrierfrequency division multiple access (SC-FDMA) scheme for an uplink (UL).UL denotes a wireless link for transmitting data or a control signal bya terminal to a base station, and DL denotes a wireless link fortransmitting data or a control signal by a base station to a terminal.In the multiple access schemes described above, time-frequency resourcesfor carrying data or control information are allocated and managed in amanner to prevent overlapping of the resources between users, i.e., toestablish the orthogonality, in order to identify data or controlinformation of each user.

A future communication system after LTE, i.e., a 5G communicationsystem, should freely apply various requirements from a user, a serviceprovider, etc., in order to support a service satisfying all of thevarious requirements. Services considered for 5G communication systemsmay include enhanced mobile broadband (eMBB), massive machine typecommunication (mMTC), ultra-reliability low-latency communication(URLLC), etc.

The purpose of eMBB is to provide a data rate enhanced more than a datarate supported by the existing LTE, LTE-A, or LTE-Pro. For example, in a5G communication system, eMBB should provide a peak data rate of 10 Gbpsfor UL and a peak data rate of 20 Gbps for DL in view of a single basestation. The 5G communication system should also provide the peak datarates and an increased user perceived data rate of a terminal.

In order to satisfy the requirements described above, a 5G communicationsystem requires the improvement of various transmission/receptiontechnologies including further enhanced MIMO transmission technology.

In addition, while current LTE uses, for the transmission of a signal, amaximum transmission bandwidth of 20 MHz in a band of 2 GHz allocated toin LTE, a 5G communication system uses a frequency bandwidth greaterthan 20 MHz in a frequency band of 3-6 GHz or a frequency band of 6 GHzor greater to satisfy a data transfer rate required for the 5Gcommunication system.

In a 5G communication system, mMTC has been considered to supportapplication services such as the IoT. mMTC requires the support ofmassive terminal connection in a cell, the improvement of terminalcoverage, improved battery lifetime, terminal cost reduction, etc., inorder to efficiently provide the IoT. Because IoT is often mounted invarious sensors and devices to provide communication functions, mMTC isalso required to support many terminals (e.g., 1,000,000 terminals/km2)in a cell. A terminal supporting mMTC requires a wider coverage comparedto other services provided in a 5G communication system because, due tothe nature of mMTC, it is probably that the terminal will be disposed ina radio shadow area, such as the basement of a building, which a cellfails to cover. A terminal supporting mMTC is required to be inexpensiveand have a very long battery life of, e.g., 10-15 years, because it ishard to often change the battery of the terminal.

URLLC is a cellular-based wireless communication service used for aparticular purpose (e.g., mission-critical). Services used in remotecontrol for robots or machinery, industrial automation, unmanned aerialvehicle, remote health care, emergency alert, etc., may be consideredfor URLLC. Therefore, communication provided by URLLC should providevery low latency and very high reliability. For example, a servicesupporting URLLC should satisfy a wireless connection latency time(e.g., air interface latency) smaller than 0.5 milliseconds and a packeterror rate of 10-5 or smaller at the same time. Therefore, for servicessupporting URLLC, a 5G system requires a design for providing atransmission time interval (TTI) shorter than those of other servicesand allocating a wide domain of resources in a frequency band to securethe reliability of a communication link.

Three services of 5G technology, i.e., eMBB, URLLC, and mMTC, may bemultiplexed and then transmitted in a single system. In order to satisfydifferent requirements of the services, different transmission/receptionschemes and different transmission/reception parameters may be used forthe services, respectively.

FIG. 1 illustrates a time-frequency domain in a 5G system according toan embodiment.

Referring to FIG. 1 , the horizontal axis indicates a time domain, andthe vertical axis indicates a frequency domain. In the time-frequencydomain, a basic unit of a resource may be defined as a resource element(RE) 101, i.e., one OFDM symbol 102 in the time axis and one subcarrier103 in the frequency axis. In the frequency domain, N^(RB) _(SC)consecutive REs (e.g., 12) may configure a single resource block (RB)104. One subframe 110 may be configured by N symbols 102, and the lengthof the subframe may be 1.0 ms. The number of the symbols (N) included inone subframe 110 may be different according to subcarrier spacing.

FIG. 2 illustrates a frame, subframe, and slot structure in a 5G systemaccording to an embodiment.

Referring to FIG. 2 , a frame 200 includes a subframe 201, whichincludes a slot 202 or 203. The frame 200 may be defined as 10 ms, wherethe subframe 201 is defined as 1 ms, and thus the frame 200 may beconfigured by a total of 10 subframes 201. One slot 202 or 203 may bedefined as 14 OFDM symbols (i.e., the number (N^(slot) _(symb)) ofsymbols per one slot=14). One subframe 201 may be configured by one slot202 or a plurality of slots 203, and the number of slots 202 or 203 perone subframe 201 may be different according to a configuration value p204 or 205 of subcarrier spacing.

FIG. 2 illustrates examples in which a subcarrier spacing configurationvalue μ 204 is 0, and a subcarrier spacing configuration value μ 205is 1. If μ is 0 (204), one subframe 201 may be configured by one slot202. If μ is 1 (205), one subframe 201 may be configured by two slots203. That is, the number of slots per one subframe (N^(subframe)_(slot)) may be different according to a configuration value μ of asubcarrier spacing, and according thereto, the number of slots per oneframe (N^(frame) _(slot)) may be different. N^(subframe) _(slot)andN^(frame) _(slot) according to each subcarrier spacing configuration μmay be defined as shown below in Table 1.

TABLE 1 μ N_(symb) ^(slot) N_(slot) ^(frame,μ) N_(slot) ^(subframe,μ) 014  10  1 1 14  20  2 2 14  40  4 3 14  80  8 4 14 160 16 5 14 320 32

FIG. 3 illustrates a configuration of a BWP in a 5G communication systemaccording to an embodiment.

Referring to FIG. 3 , a terminal bandwidth 300 is configured to bedivided into two BWPs, BWP #1 301 and BWP #2 302. A base station mayconfigure one BWP or a plurality of BWPs for a terminal and mayconfigure information shown in Table 2 below for each BWP.

TABLE 2 BWP ::= SEQUENCE { bwp-Id BWP-Id,  (bandwidth part identifier)locationAndBandwidth INTEGER (1..65536), (bandwidth part location)subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5}, (subcarrierspacing) cyclicPrefix ENUMERATED { extended } (cyclic prefix) }

In addition to the configuration information described above, variousparameters related to a BWP may be configured for the terminal. Theinformation may be transferred by the base station to the terminalthrough higher layer signaling, e.g., radio resource control (RRC)signaling. At least one BWP among the configured one BWP or plurality ofBWPs may be activated. Whether the configured BWP is activated may besemi-statically transferred from the base station to the terminalthrough RRC signaling, or dynamically transferred through DCI.

An initial BWP for an initial access may be configured for the terminalbefore an RRC connection by the base station through a masterinformation block (MIB). More specifically, a terminal may receivecontrol information relating to a CORESET and a search space, in which aphysical downlink control channel (PDCCH) can be transmitted, the PDCCHbeing designed for the terminal to receive system information for aninitial access through an MIB in an initial access stage. For example,system information for an initial access may correspond to remainingsystem information (RMSI) or system information block 1 (SIB1).

A CORESET and a search space that are configured through an MIB may beassumed to be identifiers (IDs) 0. The base station may notify theterminal of configuration information such as frequency allocationinformation, time allocation information, and numerology for CORESET #0through an MIB. In addition, the base station may notify the terminal ofconfiguration information relating to a monitoring period and occasionfor CORESET #0, i.e., configuration information for CORESET #0, throughan MIB. The terminal may consider a frequency region configured to beCORESET #0 obtained from an MIB, as an initial BWP for an initialaccess. The ID of the initial BWP may be 0.

The BWP configuration supported by 5G may be used for various purposes.

For example, if a bandwidth supported by the terminal is smaller than asystem bandwidth, the terminal may be supported through the BWPconfiguration. The frequency location (configuration information 2) of aBWP may be configured for the terminal so that the terminal transmits orreceives data at a particular frequency location in a system bandwidth.

As another example, the base station may configure a plurality of BWPsfor a terminal in order to support different numerologies. In order tosupport, to a terminal, both data transmission/reception using asubcarrier spacing of 15 KHz and data transmission/reception using asubcarrier spacing of 30 KHz, the base station may configure, for theterminal, two BWPs having a subcarrier spacing of 15 KHz and asubcarrier spacing of 30 KHz, respectively. Different BWPs may undergofrequency division multiplexing, and if the terminal and the basestation are to transmit or receive data using a particular subcarrierspacing, a BWP configured to have the subcarrier spacing may beactivated.

As another example, the base station may configure BWPs having differentbandwidths for the terminal in order to reduce the power consumption ofthe terminal. If the terminal supports a very wide bandwidth, such as100 MHz, and always transmits or receives data through the bandwidth,the terminal may consume a very large quantity of power. Particularly,unnecessary monitoring of a DL control channel in a large bandwidth of100 MHz under no traffic is very inefficient in view of powerconsumption. In order to reduce the power consumption of a terminal, thebase station may configure a BWP having a relatively small bandwidth,such as 20 MHz, for the terminal. If there is no traffic, the terminalmay monitor a 20 MHz BWP, and if data is generated, the terminal maytransmit or receive the data through a 100 MHz BWP according to anindication of the base station.

In relation to a method for configuring a BWP described above,terminals, before being RRC-connected, may receive configurationinformation of an initial BWP through an MIB in an initial access stage.A CORESET for a DL control channel through which DCI scheduling an SIBmay be transmitted may be configured for the terminal through an MIB ofa physical broadcast channel (PBCH). The bandwidth of the CORESETconfigured by the MIB may be considered as an initial BWP, and theterminal may receive a physical downlink shared channel (PDSCH) throughwhich the SIB is transmitted, through the configured initial BWP. Inaddition to the reception of an SIB, an initial BWP may be used forother system information (OSI), paging, and random access.

If one or more BWPs are configured for the terminal, the base stationmay instruct the terminal to change a BWP, by using a BWP indicatorfield in the DCI. For example, referring again to FIG. 3 , if acurrently activated BWP of the terminal is BWP #1 301, the base stationmay indicate BWP #2 302 to the terminal through a BWP indicator in theDCI, and the terminal may change the BWP to BWP #2 302 as indicated bythe BWP indicator in the received DCI.

In a wireless communication system supporting frequency divisionduplexing (FDD), change of a UL BWP may be indicated by DCI (e.g., DCIformat 0_1) scheduling UL data transmitted through a physical uplinkshared channel (PUSCH), and change of a DL BWP may be indicated by DCI(e.g. DCI format 1_1) scheduling DL data received through a PDSCH.

In a wireless communication system supporting time division duplexing(TDD), a UL BWP and a DL BWP having the same BWP index may be related,and both the UL BWP and the DL BWP may be changed by a BWP indicatorindicated by DCI (e.g., a DCI format 0_1 or 1_1) scheduling a PUSCH or aPDSCH. For example, if a currently activated BWP is BWP #1, BWP #1 isactivated in both UL/DL BWPs in TDD. If a change to BWP #2 is indicatedby DCI format 0_1(or 1_1), the terminal may change both the UL/DL BWPsto BWPs #2.

As described above, a BWP change based on DCI may be indicated by DCIscheduling a PDSCH or a PUSCH. After a terminal receives a BWP changerequest, the terminal should transmit or receive the PDSCH or PUSCHscheduled by the DCI in a changed BWP within a certain time frame. Tothis end, a standard prescribes a requirement for a latency timeinterval (T_(BWP)) required for a BWP change, and the requirements maybe defined, e.g., as shown below in Table 3. The requirements for BWPchange latency time interval may support type 1 or type 2 according tothe capability of the terminal. The terminal may report a supportabletype of BWP latency time interval to the base station.

TABLE 3 NR Slot BWP switch length delay T_(BWP) (slots) μ (ms) Type1^(Note 1) Type 2^(Note 1) 0 1   [1]  [3] 1 0.5 [2]  [5] 2  0.25 [3] [9] 3  0.125 [6] [17] Note 1: Depends on UE capability. Note 2: If theBWP switch involves changing of subcarrier spacing (SCS), the BWP switchdelay is determined by the larger one between the SCS before BWP switchand the SCS after BWP switch.

According to the above requirements for BWP change latency timeinterval, if the terminal receives DCI including a BWP change indicatorin slot n, the terminal should complete changing to a new BWP indicatedby the BWP change indicator no later than slot n+T_(BWP), and transmitor receive a data channel scheduled by the DCI in the new BWP.

If the base station is to schedule a data channel in a new BWP, the basestation may determine time domain resource allocation for the datachannel in consideration of a BWP change latency time interval of theterminal. That is, in a method of determining time domain resourceallocation for a data channel, when the base station schedules the datachannel in a new BWP, the data channel may be scheduled after a BWPchange latency time interval.

In a 5G system, scheduling information on UL data (or a physical UL datachannel (e.g., a PUSCH)) or DL data (or a physical DL data channel(e.g., a PDSCH)) may be transferred through DCI from a base station to aterminal. The terminal may monitor a fallback DCI format and anon-fallback DCI format for a PUSCH or a PDSCH. The fallback DCI formatmay be configured by a field pre-defined between a base station and aterminal, and the non-fallback DCI format may include a configurablefield.

The DCI may undergo a channel coding and modulation process, and then betransmitted through a PDCCH. A cyclic redundancy check (CRC) is attachedto a payload of a DCI message, and the CRC is scrambled by a radionetwork temporary identifier (RNTI) corresponding to the terminal ID.Different types of RNTIs may be used according to the purpose of a DCImessage, e.g., UE-specific data transmission, a power control command, arandom access response, etc. That is, an RNTI is not explicitlytransmitted, and is transmitted after being included in a CRCcalculation process. If the terminal has received a DCI messagetransmitted on a PDCCH, the terminal may identify a CRC by using anassigned RNTI. If a CRC identification result is correct, the terminalmay identify that the message has been transmitted to the terminal. Forexample, DCI scheduling a PDSCH for system information (SI) may bescrambled by an SI-RNTI. DCI scheduling a PDSCH for a random accessresponse (RAR) message may be scrambled by a random access (RA)-RNTI(RA-RNTI). DCI scheduling a PDSCH for a paging (P) message may bescrambled by a P-RNTI. DCI notifying of a slot format indicator (SFI)may be scrambled by an SFI-RNTI. DCI notifying of a transmit powercontrol (TPC) may be scrambled by a TPC-RNTI. DCI scheduling aUE-specific PDSCH or PUSCH may be scrambled by a cell (C)-RNTI (C-RNTI).

DCI format 0_0 may be used for fallback DCI scheduling a PUSCH, and aCRC may be scrambled by a C-RNTI. DCI format 0_0 having a CRC scrambledby a C-RNTI may include information as shown below in Table 4.

TABLE 4      -   Identifier for DCI formats (DCI format identifier)- [1]bit    -   Frequency   domain   resource   assignment   - [┌log₂(N_(RB)^(UL,BWP)(N_(RB) ^(UL,BWP) +1)/2┐] bits    -   Time domain resourceassignment - X bits    -   Frequency hopping flag - 1 bit.   -   Modulation and coding scheme - 5 bits    -   New data indicator -1 bit    -   Redundancy version - 2 bits    -   Hybrid automatic repeatrequest (HARQ) process number - 4 bits    -   TPC command for scheduledPUSCH (wherein TPC indicates transmit power control) - 2 bits   -   UL/supplementary uplink (SUL) indicator - 0 or 1 bit

DCI format 0_1 may be used for non-fallback DCI scheduling a PUSCH, anda CRC may be scrambled by a C-RNTI. DCI format 0_1 having a CRCscrambled by a C-RNTI may include information as shown below in Table 5.

TABLE 5 - Identifier for DCI formats - 1 bits - Carrier indicator - 0 or3 bits - UL/SUL indicator - 0 or 1 bit - BWP indicator - 0, 1 or 2bits - Frequency domain resource assignment • For resource allocationtype 0, ┌N_(RB) ^(UL,BWP) / P┐ bits • For resource allocation type 1,┌log₂(N_(RB) ^(UL,BWP)(N_(RB) ^(UL,BWP) + 1)/2┐ bits - Time domainresource assignment -1, 2, 3, or 4 bits - Frequency hopping flag - 0 or1 bit, only for resource allocation type 1. • 0 bit if only resourceallocation type 0 is configured; • 1 bit otherwise. - Modulation andcoding scheme - 5 bits - New data indicator - 1 bit - Redundancyversion - 2 bits - HARQ process number - 4 bits - 1st DL assignmentindex - 1 or 2 bits • 1 bit for semi-static HARQ-acknowledgement (ACK)codebook; • 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACKcodebook. - 2nd DL assignment index - 0 or 2 bits • 2 bits for dynamicHARQ-ACK codebook with two HARQ-ACK sub-codebooks; • 0 bit otherwise. -TPC command for scheduled PUSCH - 2 bits $\begin{matrix}{‐{{Sounding}{reference}{signal}({SRS}){resource}{indicator}}‐} \\{\left\lceil {\log_{2}\left( {\sum\limits_{k = 1}^{L_{\max}}\begin{pmatrix}N_{SRS} \\k\end{pmatrix}} \right)} \right\rceil{or}\left\lceil {\log_{2}\left( N_{SRS} \right)} \right\rceil{bits}}\end{matrix}$ $\begin{matrix}{{\left\lceil {\log_{2}\left( {\sum\limits_{k = 1}^{L_{\max}}\begin{pmatrix}N_{SRS} \\k\end{pmatrix}} \right)} \right\rceil{bits}{for}{non}}‐{{codebook}{based}{PUSCH}}} \\{{{transmission}\left( {{if}{PUSCH}{transmission}{is}{not}{based}{on}{codebook}} \right)};}\end{matrix}$ • ┌log₂(N_(SRS))┐ bits for codebook based PUSCHtransmission (if PUSCH transmission is based on codebook). - Precodinginformation and number of layers -up to 6 bits - Antenna ports - up to 5bits - SRS request - 2 bits - Channel state information (CSI) request -0, 1, 2, 3, 4, 5, or 6 bits - Code block group (CBG) transmissioninformation - 0, 2, 4, 6, or 8 bits - Phase tracking referencesignal-demodulation reference signal (PTRS-DMRS) - 0 or 2 bits. -beta_offset indicator - 0 or 2 bits - DMRS sequence initialization - 0or 1 bit - UL-SCH indicator − 1 bit

DCI format 1_0 may be used for fallback DCI scheduling a PDSCH, and aCRC may be scrambled by a C-RNTI. DCI format 1_0 having a CRC scrambledby a C-RNTI may include information as shown below in Table 6.

TABLE 6      -   Identifier for DCI formats - 1 bit   -   Frequency   domain   resource   assignment   - [┌log₂(N_(RB)^(DL,BWP)(N_(RB) ^(DL,BWP) +1)/2┐] bits    -   Time domain resourceassignment - X bits    -   Virtual resource block (VRB)-to-physicalresource block (PRB) mapping - 1 bit.    -   Modulation and codingscheme - 5 bits    -   New data indicator - 1 bit    -   Redundancyversion - 2 bits    -   HARQ process number - 4 bits    -   DLassignment index - 2 bits    -   TPC command for scheduled physicaluplink control channel (PUCCH) - 2 bits    -   PUCCH resourceindicator - 3 bits    -   PDSCH-to-HARQ feedback timing indicator - 3bits

DCI format 1_1 may be used for non-fallback DCI scheduling a PDSCH, anda CRC may be scrambled by a C-RNTI. DCI format 1_1 having a CRCscrambled by a C-RNTI may include information as shown below in Table 7.

TABLE 7      -   Identifier for DCI formats - 1 bits    -   Carrierindicator - 0 or 3 bits    -   BWP indicator - 0, 1 or 2 bits   -   Frequency domain resource assignment    ·   If resourceallocation type 0 is configured, N_(RBG) bits   ·   If   resource   allocation   type   1   is   configured,[┌log₂(N_(RB) ^(DL,BWP)(N_(RB) ^(DL,BWP) +1)/2┐] bits    ·   If bothresource allocation type 0 and 1 is configured,    -   max(┌log₂(N_(RB)^(DL,BWP)(N_(RB) ^(DL,BWP) +1)/2┐ , N_(RBG))+1 bits    -   Time domainresource assignment -1, 2, 3, or 4 bits    -   VRB-to-PRB mapping - 0 or1 bit, only for resource allocation type 1.    ·   0 bit if onlyresource allocation type 0 is configured;    ·   1 bit otherwise.   -   PRB bundling size indicator (wherein PRB indicates) - 0 or 1 bit   -   Rate matching indicator - 0, 1, or 2 bits    -   Zero power (ZP)CSI-reference signal (RS) trigger - 0, 1, or 2 bits    For transportblock 1:    -   Modulation and coding scheme - 5 bits    -   New dataindicator - 1 bit    -   Redundancy version - 2 bits    For transportblock 2:    -   Modulation and coding scheme - 5 bits    -   New dataindicator - 1 bit    -   Redundancy version - 2 bits    -   HARQ processnumber - 4 bits    -   DL assignment index - 0 or 2 or 4 bits    -   TPCcommand for scheduled PUCCH - 2 bits    -   PUCCH resource indicator - 3bits    -   PDSCH-to-HARQ_feedback timing indicator - 3 bits   -   Antenna, ports - 4, 5 or 6 bits    -   Transmission configurationindication - 0 or 3 bits    -   SRS request - 2 bits    -   CBGtransmission information - 0, 2, 4, 6, or 8 bits    -   CBG flushing outinformation - 0 or 1 bit    -   DMRS sequence initialization - 1 bit

FIG. 4 illustrates a CORESET on which a DL control channel istransmitted in a 5G wireless communication system according to anembodiment.

Referring to FIG. 4 , a BWP 410 of a terminal is configured along afrequency axis and two CORESETs (CORESET #1 401 and CORESET #2 402) areconfigured in one slot 420 along a time axis. The CORESETs 401 and 402may be configured on a particular frequency resource 403 in the entireterminal BWP 410 along the frequency axis. The CORESETs 401 and 402 maybe configured by one OFDM symbol or a plurality of OFDM symbols alongthe time axis, and the configured OFDM symbol or symbols may be definedas a CORESET duration 404. In FIG. 4 , CORESET #1 401 is configured tohave a CORESET duration of two symbols, and CORESET #2 402 is configuredto have a CORESET duration of one symbol.

A CORESET in 5G, described above may be configured for a terminal by abase station through higher layer signaling (e.g. system information,MIB, and RRC signaling). Configuring of a CORESET for a terminalincludes providing information such as a CORESET identity, the frequencylocation of the CORESET, the symbol length of the CORESET, etc. Forexample, the information may include information as shown below in Table8.

TABLE 8 ControlResourceSet ::= SEQUENCE {  -- Corresponds to L1parameter ′CORESET-ID′  controlResourceSetId ControlResourceSetId, (control resource set identifier(Identity))  frequencyDomainResourcesBIT STRING (SIZE (45)),  (frequency axis resource assignmentinformation)  duration INTEGER (1..maxCoReSetDuration),  (time axisresource assignment information)  cce-REG-MappingType CHOICE { (CCE-to-REG mapping scheme)   interleaved SEQUENCE {    reg-BundleSizeENUMERATED {n2, n3, n6},    (REG bundle size)    precoderGranularityENUMERATED {sameAsREG- bundle, allContiguousRBs},    interleaverSizeENUMERATED {n2, n3, n6}    (interleaver size)    shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1)  OPTIONAL    (interleavershift)    },  nonInterleaved NULL  },  tci-StatesPDCCHSEQUENCE(SIZE (1..maxNrofTCI- StatesPDCCH)) OF TCI-StateId OPTIONAL, (Quasi-co-location (QCL) configuration information)  tci-PresentInDCIENUMERATED {enabled}    }

In Table 8, tci-StatesPDCCH (simply referred to as a TCI state)configuration information may include information on the index orindices of one or multiple synchronization signal(SS)/PBCH blocks havinga quasi-co-located (QCL) relationship with a demodulation referencesignal (DMRS) transmitted on a corresponding CORESET, or information onthe index of a CSI reference signal (CSI-RS).

FIG. 5 illustrates a basic unit structure of time and frequencyresources of a DL control channel in 5G according to an embodiment.

Referring to FIG. 5 , a basic unit of time and frequency resources of acontrol channel is a resource element group (REG) 503, and the REG 503may be defined as one OFDM symbol 501 in a time axis and one physicalresource block (PRB) 502 in a frequency axis, i.e., may be defined as 12subcarriers. The REGs 503 may be connected to each other to configure aDL control channel assignment unit.

If a basic unit for the assignment of a DL control channel in 5Gtechnology is a control channel element (CCE) 504, one CCE 504 may beconfigured by a plurality of the REGs 503. The REG 503 may be configuredby 12 REs, one CCE 504 may be configured by six REGs 503, and the oneCCE 504 may be configured by 72 REs. If a DL CORESET is configured, theresource set may be configured by a plurality of CCEs 504. A particularDL control channel may be transmitted after being mapped to one CCE 504or a plurality of CCEs 504 according to an aggregation level (AL) in theCORESET. CCEs 504 in a CORESET are distinguished by numbers, and thenumbers may be assigned according to a logical mapping scheme.

The REG 503 may include REs to which DCI is mapped and a region to whicha DMRS 505, which is a reference signal for decoding the REs, is mapped.In FIG. 5 , three DMRSs 505 are transmitted in one REG 503 as anexample.

The number of CCEs required for transmitting a PDCCH may be 1, 2, 4, 8,and 16 according to ALs, and different numbers of CCEs may be used toimplement the link adaptation of the DL control channel. For example, ifAL=L, one DL control channel may be transmitted through L number ofCCEs. A terminal should detect a signal while the terminal does not knowinformation relating to a DL control channel, and a search spaceindicating a set of CCEs is defined for blind decoding. A search spaceis a set of DL control channel candidates configured by CCEs to whichthe terminal is required to attempt to decode at a given AL, and becausethere are various ALs grouping 1, 2, 4, 8, and 16 CCEs into one,respectively, the terminal has a plurality of search spaces. A searchspace set may be defined at all of the configured ALs.

A search space may be classified as a common search space and aUE-specific search space. A group of terminals or all the terminals mayinvestigate a common search space for a PDCCH in order to receivecell-common control information such as a paging message or dynamicscheduling for system information. For example, the terminals mayinvestigate a common search space for a PDCCH to receive PDSCHscheduling assignment information for transmission of an SIB includingcell operator information. For a common search space, a particular groupof terminals or all the terminals are required to receive a PDCCH, andthus the common search space may include a pre-determined set of CCEs.

The terminals may investigate a UE-specific search space for a PDCCH inorder to receive scheduling assignment information for a UE-specificPDSCH or PUSCH. A UE-specific search space may be defined for a specificUE by using the identity of the UE and the functions of various systemparameters.

In 5G, a parameter for a search space for a PDCCH may be configured fora terminal by a base station through higher layer signaling (e.g., anSIB, an MIB, and RRC signaling). For example, the base station mayconfigure, for the terminal, the number of PDCCH candidates at each ALL, a monitoring period for a search space, a monitoring occasion in theunits of symbols in a slot of a search space, a search space type (i.e.,a common search space or a UE-specific search space), a combination ofan RNTI and a DCI format to be monitored in a corresponding searchspace, and an index of a CORESET in which a search space is to bemonitored. The configured information may include information as shownbelow in Table 9.

TABLE 9 Searchspace ::= SEQUENCE {  -- Identity of the search space.SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB)or ServingCellConfigCommon.  searchSpaceId SearchSpaceId,  (search spaceidentifier)  controlResourceSetId ControlResourceSetId,  (controlresource set identifier)  monitoringSlotPeriodicityAndOffset CHOICE { (monitoring slot level period)   sl1 NULL,   sl2 INTEGER (0..1),   sl4INTEGER (0..3),   sl5 INTEGER (0..4),   sl8 INTEGER (0..7),   sl10INTEGER (0..9),   sl16 INTEGER (0..15),   sl20 INTEGER (0..19)  } monitoringSymbolsWithinSlot BIT STRING (SIZE (14))  (monitoring symbolsin slot)  nrofCandidates SEQUENCE {  (the number of PDCCH candidates foreach aggregation level)   aggregationLevel1 ENUMERATED {n0, n1, n2, n3,n4, n5, n6, n8},   aggregationLevel 2 ENUMERATED {n0, n1, n2, n3, n4,n5, n6, n8},   aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6,n8},   aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},  aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}  } searchSpaceType CHOICE {  (search space type)   -- Configures thissearch space as common search space (CSS) and DCI formats to monitor.  common SEQUENCE {  (common search space)   }   ue-Specific SEQUENCE { (UE-specific search space)    --Indicates whether the UE monitors inthis UE-specific search space (USS) for DCI formats 0-0 and 1-0 or forformats 0-1 and 1-1.    formats ENUMERATED {formats0-0- And-1-0,formats0-1-And-1-1},    ...   }

The base station may configure one search space set or a plurality ofsearch space sets for the terminal according to the configurationinformation. The base station may configure, for the terminal, searchspace set 1 and search space set 2, in search space set 1, DCI format Ascrambled by X-RNTI may be configured to be monitored in a common searchspace, and in search space set 2, DCI format B scrambled by Y-RNTI maybe configured to be monitored in a UE-specific search space.

According to the configuration information, one search space set or aplurality of search space sets may exist in a common search space or aUE-specific search space. Search space set #1 and search space set #2may be configured to be common search spaces, and search space set #3and search space set #4 may be configured to be UE-specific searchspaces.

In a common search space, combinations of a DCI format and an RNTI asbelow may be monitored.

-   -   DCI format 0_0/1_0 with CRC scrambled by C-RNTI, Configured        Scheduling RNTI (CS-RNTI), Semi-Persistent (SP)-CSI-RNTI,        RA-RNTI, Temporary Cell RNTI (TC-RNTI), P-RNTI, or SI-RNTI    -   DCI format 2_0 with CRC scrambled by SFI-RNTI    -   DCI format 2_1 with CRC scrambled by Interruption RNTI        (INT-RNTI)    -   DCI format 2_2 with CRC scrambled by Transmit Power Control for        PUSCH RNTI (TPC-PUSCH-RNTI, or Transmit Power Control for PUCCH        RNTI (TPC-PUCCH-RNTI)    -   DCI format 2_3 with CRC scrambled by Transmit Power Control for        SRS RNTI (TPC-SRS-RNTI)

In a UE-specific search space, combinations of a DCI format and an RNTIas shown below may be monitored.

-   -   DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI, or        TC-RNTI    -   DCI format 1_0/1_1 with CRC scrambled by C-RNTI, CS-RNTI, or        TC-RNTI

The described types of RNTIs may follow the definitions below.

-   -   C-RNTI: for scheduling a UE-specific PDSCH    -   TC-RNTI: for scheduling a UE-specific PDSCH    -   CS-RNTI: for scheduling semi-statically configured UE-specific        PDSCH/PUSCH    -   RA-RNTI: for scheduling a PDSCH in a random access stage    -   P-RNTI: for scheduling a PDSCH on which paging is transmitted    -   SI-RNTI: for scheduling a PDSCH on which system information is        transmitted    -   INT-RNTI: for notifying of whether a PDSCH is punctured    -   TPC-PUSCH-RNTI: for indicating a power control command for a        PUSCH    -   TPC-PUCCH-RNTI: for indicating a power control command for a        PUCCH    -   TPC-SRS-RNTI: for indicating a power control command for an SRS

The described DCI formats may follow the definitions shown below inTable 10.

TABLE 10 DCI format Usage 0_0 Scheduling of a PUSCH in one cell 0_1Scheduling of a PUSCH in one cell 1_0 Scheduling of a PDSCH in one cell1_1 Scheduling of a PDSCH in one cell 2_0 Notifying a group of UEs ofthe slot format 2_1 Notifying a group of UEs of the PRB(s) and OFDMsymbol(s) where UE may assume no transmission is intended for the UE 2_2Transmission of TPC commands for a PUCCH and a PUSCH 2_3 Transmission ofa group of TPC commands for SRS transmissions by one or more UEs

A base station may configure, for a terminal, time domain resourceallocation information (e.g., a table) for a DL data channel (e.g., aPDSCH) and a uplink data channel (e.g., a PUSCH) through higher layersignaling (e.g., RRC signaling). The base station may configure, for aPDSCH, a table configured by a maximum of 16 entries(maxNrofDL-Allocations=16), and may configure, for a PUSCH, a tableconfigured by a maximum of 16 entries (maxNrofUL-Allocations=16). Timedomain resource allocation (TD-RA) information may includePDCCH-to-PDSCH slot timing (i.e., a time gap in units of slots, betweena time point at which a PDCCH is received, and a time point at which aPDSCH scheduled by the received PDCCH is transmitted, e.g., the timingis indicated by K0) or PDCCH-to-PUSCH slot timing (i.e., a time gap inunits of slots, between a time point at which a PDCCH is received, and atime point at which a PUSCH scheduled by the received PDCCH istransmitted, e.g., the timing is indicated by K₂), information relatingto the location of a starting symbol of a PDSCH or a PUSCH scheduled ina slot, and the scheduled length, a mapping type of a PDSCH or a PUSCH,etc. A terminal may be notified, by a base station, of the informationas shown in Tables 11 and 12 below.

TABLE 11 PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {  k0 INTEGER(0..32)OPTIONAL, -- Need S  (PDCCH-to-PDSCH timing in units of slots) mappingType ENUMERATED {typeA, typeB},  (PDSCH mapping type) startSymbolAndLength INTEGER (0..127)  (The length and a startingsymbol of a PDSCH) }

TABLE 12 PUSCH-TimeDomainResourceAllocation information elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE(SIZE(1..maxNrofUL-Allocations) ) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {  k2 INTEGER(0..32)OPTIONAL, - - Need S  (PDCCH-to-PUSCH timing in units of slots) mappingType  ENUMERATED {typeA, typeB},  (PUSCH mapping type) startSymbolAndLength INTEGER (0..127)  (The length and a startingsymbol of a PUSCH) }

The base station may notify the terminal of one of the entries of thetable relating to the time domain resource allocation informationthrough L1 signaling (e.g., DCI). The base station may indicate one ofthe entries to the terminal through a time domain resource allocationfield in DCI. The terminal may obtain time domain resource allocationinformation relating to a PDSCH or PUSCH, based on DCI received from thebase station.

CSI may include a channel quality indicator (e.g., channel qualityinformation (CQI)), a precoding matrix index (PMI), a CSI-RS resourceindicator (CRI), an SS/PBCH block resource indicator (SSBRI), a layerindicator (LI), a rank indicator (RI), and/or an L1-reference signalreceived power (RSRP). A base station may control time and frequencyresources for measuring and reporting the above CSI of a terminal.

In order to measure and report of the CSI, N(≥1) setting information(CSI-ReportConfig) for CSI reporting, M(≥1) configuration information(CSI-ResourceConfig) for a RS transmission resource, and one or twotrigger state (CSI-AperiodicTriggerStateList,CSI-SemiPersistentOnPUSCH-TriggerStateList) list information may beconfigured for the terminal through higher layer signaling.

The above-described configuration information for CSI measurement andreporting may be the information as shown below in Tables 13 to 19.

Table 13 illustrates a CSI-ReportConfig information element (IE) that isused to configure a periodic or semi-persistent report sent on PUCCH onthe cell in which the CSI-ReportConfig is included, or to configure asemi-persistent or aperiodic report sent on PUSCH triggered by DCIreceived on the cell in which the CSI-ReportConfig is included, in thiscase the cell on which the report is sent is determined by the receivedDCI).

TABLE 13 CSI-ReportConfig Information element -- ASN1START --TAG-CSI-REPORTCONFIG-START CSI-ReportConfig ::= SEQUENCE {  reportConfigId CSI-ReportConfigId,   carrier ServCellIndexOPTIONAL, -- Need S   resourcesForChannelMeasurementCSI-ResourceConfigId,   csi-IM-ResourcesForInterferenceCSI-ResourceConfigId OPTIONAL, -- Need R  nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, --Need R   reportConfigType CHOICE {     periodic SEQUENCE {      reportSlotConfig CSI- ReportPeriodicityAndOffset,      pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OFPUCCH-CSI-Resource     },     semiPersistentOnPUCCH SEQUENCE {      reportSlotConfig CSI- ReportPeriodicityAndOffset,      pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OFPUCCH-CSI-Resource     },     semiPersistentOnPUSCH SEQUENCE {      reportSlotConfig ENUMERATED {s15, s110, s120, s140, s180, s1160,s1320},       reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32),       p0alpha P0-PUSCH-AlphaSetId     },     aperiodic SEQUENCE {      reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OFINTEGER(0..32)     }   },   reportQuantity CHOICE {     none  NULL,    cri-RI-PMI-CQI   NULL,     cri-RI-i1   NULL,     cri-RI-i1-CQI  SEQUENCE {       pdsch-BundleSizeForCSI ENUMERATED {n2, n4}OPTIONAL -- Need S     },     cri-RI-CQI   NULL,     cri-RSRP  NULL,    ssb-Index-RSRP   NULL,     cri-RI-LI-PMI-CQI   NULL   },  reportFreqConfiguration SEQUENCE {     cqi-FormatIndicator ENUMERATED{ widebandCQI, subbandCQI } OPTIONAL, -- Need R     pmi-FormatIndicatorENUMERATED { widebandPMI, subbandPMI } OPTIONAL, -- Need R    csi-ReportingBand CHOICE {       subbands3 BIT STRING(SIZE(3)),      subbands4 BIT STRING(SIZE(4)),       subbands5 BITSTRING(SIZE(5)),       subbands6 BIT STRING(SIZE(6)),       subbands7BIT STRING(SIZE(7)),       subbands8 BIT STRING(SIZE(8)),      subbands9 BIT STRING(SIZE(9)),       subbands10 BITSTRING(SIZE(10)),       subbands11 BIT STRING(SIZE(11)),      subbands12 BIT STRING(SIZE(12)),       subbands13 BITSTRING(SIZE(13)),       subbands14 BIT STRING(SIZE(14)),      subbands15 BIT STRING(SIZE(15)),       subbands16 BITSTRING(SIZE(16)) ,       subbands17 BIT STRING(SIZE(17)),      subbands18 BIT STRING(SIZE(18)),       ...,       subbands19-v1530BIT STRING(SIZE(19))     } OPTIONAL -- Need S   } OPTIONAL, -- Need R  timeRestrictionForChannelMeasurements ENUMERATED {configured,notConfigured},   timeRestrictionForInterferenceMeasurements ENUMERATED{configured, notConfigured},   codebookConfig CodebookConfigOPTIONAL, -- Need R   dummy ENUMERATED {n1, n2} OPTIONAL, -- Need R  groupBasedBeamReporting CHOICE {     enabled NULL,     disabledSEQUENCE {       nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL --Need S     }   },   cqi-Table  ENUMERATED {table1, table2, table3,spare1}  OPTIONAL, -- Need R   subbandSize ENUMERATED {value1, value2},  non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig))  OF PortIndexFor8Ranks OPTIONAL,  -- Need R  ...,   [[   semiPersistentOnPUSCH-v1530  SEQUENCE {    reportSlotConfig-v1530  ENUMERATED {s14, s18, s116}   } OPTIONAL --Need R   ]] } CSI-ReportPeriodicityAndOffset ::= CHOICE {   slots4INTEGER(0..3),   slots5 INTEGER(0..4),   slots8 INTEGER(0..7),   slots10INTEGER(0..9),   slots16 INTEGER(0..15),   slots20 INTEGER(0..19),  slots40 INTEGER(0..39),   slots80 INTEGER(0..79),   slots160INTEGER(0..159),   slots320 INTEGER(0..319) } PUCCH-CSI-Resource ::=SEQUENCE {   uplinkBandwidthPartId BWP-Id,   pucch-ResourcePUCCH-ResourceId } PortIndexFor8Ranks ::= CHOICE {   portIndex8SEQUENCE{     rank1-8 PortIndex8 OPTIONAL, -- Need R     rank2-8SEQUENCE(SIZE(2)) OF PortIndex8 OPTIONAL, -- Need R     rank3-8SEQUENCE(SIZE(3)) OF PortIndex8 OPTIONAL, -- Need R     rank4-8SEQUENCE(SIZE(4)) OF PortIndex8 OPTIONAL, -- Need R     rank5-8SEQUENCE(SIZE(5)) OF PortIndex8 OPTIONAL, -- Need R     rank6-8SEQUENCE(SIZE(6)) OF PortIndex8 OPTIONAL, -- Need R     rank7-8SEQUENCE(SIZE(7)) OF PortIndex8 OPTIONAL, -- Need R     rank8-8SEQUENCE(SIZE(8)) OF PortIndex8 OPTIONAL, -- Need R   },   portIndex4SEQUENCE{     rank1-4 PortIndex4 OPTIONAL, -- Need R     rank2-4SEQUENCE(SIZE(2)) OF PortIndex4 OPTIONAL, -- Need R     rank3-4SEQUENCE(SIZE(3)) OF PortIndex4 OPTIONAL, -- Need R     rank4-4SEQUENCE(SIZE(4)) OF PortIndex4 OPTIONAL, -- Need R   },   portIndex2SEQUENCE{     rank1-2 PortIndex2 OPTIONAL, -- Need R     rank2-2SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL, -- Need R   },   portIndex1NULL } PortIndex8::= INTEGER (0..7) PortIndex4::= INTEGER (0..3)PortIndex2::= INTEGER (0..1) -- TAG-CSI-REPORTCONFIG-STOP -- ASN1STOP

  CSI-ReportConfig IE field descriptions Carrier Indicates in whichserving cell the CSI-ResourceConfig indicated below are to be found. Ifthe field is absent, the resources are on the same serving cell as thisreport configuration. codebookConfig Codebook configuration for Type-1or Type-II including codebook subset restriction. cqi-FormatIndicatorIndicates whether the UE shall report a single (wideband) or multiple(subband) CQI. cqi-Table Which CQI table to use for CQI calculation.csi-IM-ResourcesForInterference CSI IM resources for interferencemeasurement. csi-ResourceConfigId of a CSI- ResourceConfig included inthe configuration of the serving cell indicated with the field“carrierr” above. The CSI-ResourceConfig indicated here contains onlyCSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the samevalue as the bwp-Id in the CSI-ResourceConfig indicated byresourcesForChannelMeasurement. csi-ReportingBand Indicates a contiguousor non-contiguous subset of subbands in the BWP which CSI shall bereported for. Each bit in the bit-string represents one subband. Theright-most bit in the bit string represents the lowest subband in theBWP. The choice determines the number of subbands (subbands3 for 3subbands, subbands4 for 4 subbands, etc.). This field is absent if thereare less than 24 PRBs (no sub band) and present otherwise, the number ofsub bands can be from 3 (24 PRBs, sub band size 8) to 18 (72 PRBs, subband size 4). dummy This field is not used in the specification. Ifreceived it shall be ignored by the UE. groupBasedBeamReporting Turningon/off group beam based reporting. non-PMI-PortIndication Portindication for RI/CQI calculation. For each CSI-RS resource in thelinked ResourceConfig for channel measurement, a port indication foreach rank R, indicating which R ports to use. Applicable only fornon-PMI feedback. The first entry in non-PMI-PortIndication correspondsto a Non-Zero-Power (NZP)-CSI- RS-Resource indicated by the first entryin nzp-CSI-RS-Resources in the NZP-CSI-RS- ResourceSet indicated in thefirst entry of nzp-CSI-RS-ResourceSetList of the CSI- ResourceConfigwhose CSI-ResourceConfigId is indicated in a CSI-MeasId together withthe above CSI-ReportConfigId; the second entry in non-PMI-PortIndicationcorresponds to the NZP-CSI-RS-Resource indicated by the second entry innzp-CSI-RS- Resources in the NZP-CSI-RS-ResourceSet indicated in thefirst entry of nzp-CSI-RS- ResourceSetList of the sameCSI-ResourceConfig, and so on until the NZP-CSI-RS- Resource indicatedby the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry ofnzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig. Then the nextentry corresponds to the NZP-CSI-RS-Resource indicated by the firstentry in nzp-CSI-RS- Resources in the NZP-CSI-RS-ResourceSet indicatedin the second entry of nzp-CSI-RS- ResourceSetList of the same CSI-ResourceConfig and so on. nrofReportedRS The number (N) of measured RSresources to be reported per report setting in a non- group-basedreport. N <= N_max, where N_max is either 2 or 4 depending on UEcapability. When the field is absent the UE applies the value 1.nzp-CSI-RS-ResourcesForInterference NZP CSI RS resources forinterference measurement. csi-ResourceConfigId of a CSI- ResourceConfigincluded in the configuration of the serving cell indicated with thefield “carrier” above. The CSI-ResourceConfig indicated here containsonly NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is thesame value as the bwp-Id in the CSI-ResourceConfig indicated byresourcesForChannelMeasurement. p0alpha Index of the p0-alpha setdetermining the power control for this CSI report transmission.pdsch-BundleSizeForCSI PRB bundling size to assume for CQI calculationwhen reportQuantity is CRI/RI/i1/CQI. If the field is absent, the UEassumes that no PRB bundling is applied. pmi-FormatIndicator Indicateswhether the UE shall report a single (wideband) or multiple (subband)PMI. pucch-CSI-ResourceList Indicates which PUCCH resource to use forreporting on PUCCH. reportConfigType Time domain behavior of reportingconfiguration reportFreqConfiguratian Reporting configuration in thefrequency domain. reportQuantity The CSI related quantities to report.Corresponds to L1 parameter ‘ReportQuantity’. reportSlotConfigPeriodicity and slot offset. reportSlotConfig-v1530 Extended value rangefor reportSlotConfig for semi-persistent CSI on PUSCH. If the field ispresent, the UE shall ignore the value provided in the legacy field(semiPersistentOnPUSCH.reportSlotConfig). reportSlotOffsetList Timingoffset Y for semi persistent reporting using PUSCH. This field lists theallowed offset values. This list must have the same number of entries asthe pusch- TimeDomainAllocationList in PUSCH-Config. A particular valueis indicated in DCI The network indicates in the DCI field of the ULgrant, which of the configured report slot offsets the UE shall apply.The DCI value 0 corresponds to the first report slot offset in thislist, the DCI value 1 corresponds to the second report slot offset inthis list, and so on. The first report is transmitted in slot n + Y,second report in n + Y + P, where P is the configured periodicity.Timing offset Y for aperiodic reporting using PUSCH. This field liststhe allowed offset values. This list must have the same number ofentries as the pusch- TimeDomainAllocationList in PUSCH-Config. Aparticular value is indicated in DCI. The network indicates in the DCIfield of the UL grant, which of the configured report slot offsets theUE shall apply. The DCI value 0 corresponds to the first report slotoffset in this list, the DCI value 1 corresponds to the second reportslot offset in this list, etc. resourcesForChannelMeasurement Resourcesfor channel measurement. csi-ResourceConfigId of a CSI-ResourceConfigincluded in the configuration of the serving cell indicated with thefield “carrier” above. The CSI-ResourceConfig indicated here containsonly NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig isassociated with the DL BWP indicated by bwp-Id in thatCSI-ResourceConfig. subbandSize Indicates one out of two possibleBWP-dependent values for the subband size. If csi- ReportingBandisabsent, the UE shall ignore this field.timeRestrictionForChannelMeasurements Time domain measurementrestriction for the channel (signal) measurementstimeRestrictionForInterferenceMeasurements Time domain measurementrestriction for interference measurements

Table 14 provides an example of a CSI-ResourceConfig information IE thatdefines a group of one or more NZP-CSI-RS-ResourceSet, CSI-M-ResourceSetand/or CSI-SSB-ResourceSet.

TABLE 14 CSI-ResourceConfig information element -- ASN1START --TAG-CSI-RESOURCECONFIG-START CSI-ResourceConfig ::= SEQUENCE {  csi-ResourceConfigId CSI-ResourceConfigId,   csi-RS-ResourceSetListCHOICE {     nzp-CSI-RS-SSB SEQUENCE {      nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, --Need R       csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need R    },     csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId   },   bwp-Id BWP-Id,  resourceType ENUMERATED { aperiodic, semiPersistent, periodic },   ...} -- TAG-CSI-RESOURCECONFIG-STOP -- ASNISTOP

  CSI-ResourceConfig IE field descriptions bwp-Id The DL BWP in whichthe CSI-RS associated with this CSI-ResourceConfig are located.csi-ResourceConfigId Used in CSI-ReportConfig to refer to an instance ofCSI-ResourceConfig. csi-RS-ResourceSetList Contains up tomaxNrofNZP-CSI-RS- ResourceSetsPerConfig resource sets ifResourceConfigType is ‘aperiodic’ and 1 otherwise.csi-SSB-ResourceSetList List of SSB resources used for beam measurementand reporting in a resource set. resource-Type Time domain behavior ofresource configuration. Does not apply to resources provided in thecsi-SSB-ResourceSetList.

Table 15 provides an example of an NZP-CSI-RS-ResourceSet IE, whichincludes a set of NZP-CSI-RS resources (their IDs) and set-specificparameters.

TABLE 15 NZP-CSI-RS-ResourseSet information element -- ASN1START --TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE {  nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,   nzp-CSI-RS-ResourcesSEQUENCE (SIZE (1..maxNrofNZP-CSI- RS-ResourcesPerSet)) OFNZP-CSI-RS-ResourceId,   repetition ENUMERATED { on, off } OPTIONAL, --Need S   aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need S  trs-Info ENUMERATED {true} OPTIONAL, -- Need R   ... } --TAG-NZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP

  NZP-CSI-RS-ResourceSet IE field descriptions aperiodicTriggeringOffsetOffset X between the slot containing the DCI that triggers a set ofaperiodic NZP CSI-RS resources and the slot in which the CSI-RS resourceset is transmitted. The value 0 corresponds to 0 slots, value 1corresponds to 1 slot, value 2 corresponds to 2 slots, value 3corresponds to 3 slots, value 4 corresponds to 4 slots, value 5corresponds to 16 slots, value 6 corresponds to 24 slots. When thefield, is absent the UE applies the value 0. nzp-CSI-RS-ResourcesNZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set. ForCSI, there are at most 8 NZP CSI RS resources per resource set.repetition Indicates whether repetition is on/off. If the field is setto ‘OFF’, or if the field is absent, the UE may not assume that theNZP-CSI-RS resources within the resource set are transmitted with thesame DL spatial domain transmission filter and with same NrofPorts inevery symbol. Can only be configured for CSI-RS resource sets which areassociated with CSI-ReportConfig with report of LI RSRP or “no report”.trs-Info Indicates that the antenna port for all NZP-CSI-RS resources inthe CSI-RS resource set is same. If the field is absent or released theUE applies the value “false”.

Table 16 provides an example of a CSI-SSB-ResourceSet IE used toconfigure one SS/PBCH block resource set, which refers to an SS/PBCH asindicated in ServingCellConfigCommon.

TABLE 16 CSI-SSB-ResourceSet information element -- ASN1START --TAG-CSI-SSB-RESOURCESET-START CSI-SSB-ResourceSet ::= SEQUENCE {  csi-SSB-ResourceSetId CSI-SSB-ResourceSetId,   csi-SSB-ResourceList SEQUENCE (SIZE (1..maxNrofCSI-SSB- ResourcePerSet)) OF SSB-Index,   ...} -- TAG-CSI-SSB-RESOURCESET-STOP -- ASN1STOP

Table 17 provides an example of a CSI-IM-ResourceSet IE used toconfigure a set of one or more CSI Interference Management (IM)resources (e.g., their IDs) and set-specific parameters.

TABLE 17 CSI-IM-ResourceSet information element -- ASN1START --TAG-CSI-IM-RESOURCESET-START CSI-IM-ResourceSet ::= SEQUENCE {  csi-IM-ResourceSetId CSI-IM-ResourceSetId,   csi-IM-Resources SEQUENCE(SIZE(1..maxNrofCSI-IM- ResourcesPerSet)) OF CSI-IM-ResourceId,   ... }-- TAG-CSI-IM-RESOURCESET-STOP -- ASN1STOP

  CSI-IM-ResourceSet IE field descriptions csi-IM-R esourcesCSI-IM-Resources associated with this CSI-IM-ResourceSet.

Table 18 provides an example of a CSI-AperiodicTriggerStateList IE usedto configure the UE with a list of aperiodic trigger states. Eachcodepoint of the DCI field “CSI request” is associated with one triggerstate. Upon reception of the value associated with a trigger state, theUE will perform measurement of CSI-RSs and aperiodic reporting on L1according to all entries in the associatedReportConfigInfoList for thattrigger state.

TABLE 18 CSI-AperiodicTriggerStateList information element -- ASN1START-- TAG-CSI-APERIODICTRIGGERSTATELIST-STARTCSI-AperiodicTriggerStateList  ::= SEQUENCE  (SIZE  (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerStateCSI-AperiodicTriggerState ::= SEQUENCE {  associatedReportConfigInfoList SEQUENCE(SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo,   ... } CSI-AssociatedReportConfigInfo ::=SEQUENCE {   reportConfigId CSI-ReportConfigId,   resourcesForChannelCHOICE {     nzp-CSI-RS SEQUENCE {       resourceSet INTEGER(1..maxNrofNZP-CSI-RS- ResourceSetsPerConfig),       qcl-info SEQUENCE (SIZE (1..maxNrofAP-CSI-RS- ResourcesPerSet)) OF TCI-StateId OPTIONAL --Cond Aperiodic     },     csi-SSB-ResourceSet INTEGER(1..maxNrofCSI-SSB- ResourceSetsPerConfig)   },  csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig)    OPTIONAL, -- Cond CSI-IM-ForInterference  nzp-CSI-RS-ResourcesForInterference   INTEGER   (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)  OPTIONAL, -- Cond NZP-CSI-RS-ForInterference  ... } -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP -- ASN1STOP

  CSI-AssociatedReportConfigInfo IE field descriptionscsi-IM-ResourcesForInterference CSI-IM-ResourceSet for interferencemeasurement. Entry number in csi-IM-ResourceSetList in theCSI-ResourceConfig indicated by csi-IM- ResourcesForInterference in theCSI-ReportConfig indicated by reportConfigId above (1 corresponds to thefirst entry, 2 to the second entry, etc.). The indicated CSI-IM-ResourceSet should have the same number of resources as theNZP-CSI-RS-ResourceSet indicated in nzp-CSI-RS-ResourcesforChannel.csi-SSB-ResourceSet CSI-SSB-ResourceSet for channel measurements. Entrynumber in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated byresourcesForChannelMeasurement in the CSI-ReportConfig indicated byreportConfigId above (1 corresponds to the first entry, 2 to the secondentry, etc.). nzp-CSI-RS-ResourcesForInterference NZP-CSI-RS-ResourceSetfor interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated bynzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated byreportConfigId above (1 corresponds to the first entry, 2 to the secondentry, etc.). qcl-info List of references to TCI-States tor providingthe QCL source and QCL type for each NZP-CSI-RS-Resource listed innzp-CSI-RS- Resources of the NZP-CSI-RS-ResourceSet indicated bynzp-CSI-RS-ResourcesforChannel. Each TCI-StateId refers to the TCI-Statewhich has this value for tci-StateId and is defined intci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlinkcorresponding to the serving cell and to the DL BWP to which theresourcesForChannelMeasurement (in the CSI-ReportConfig indicated byreportConfigId above) belong to. First entry in qcl-info-forChannelcorresponds to first entry in nzp-CSI-RS-Resources of thatNZP-CSI-RS-ResourceSet, second entry in qcl-info-forChannel correspondsto second entry in nzp-CSI-RS- Resources, etc. reportConfigId ThereportConfigId of one of the CSI-ReportConfigToAddMod configured inCSI-MeasConfig. resourceSet NZP-CSI-RS-ResourceSet for channelmeasurements. Entry number in nzp-CSI-RS- ResourceSetList in theCSI-ResourceConfig indicated by resourcesForChannelMeasurement in theCSI-ReportConfig indicated by reportConfigId above (1 corresponds to thefirst entry, 2 to the second entry, etc.).

Conditional Presence Explanation Aperiodic The field is mandatorypresent if the NZP-CSI-RS-Resources in the associated resourceSet havethe resourceType aperiodic. The field is absent otherwise. CSI-IM-ForInterference This field is optional need M if the CSI-ReportConfigidentified by reportConfigId is configured with csi-IM-ResourcesForInterference; otherwise it is absent. NZP-CSI-RS- This fieldis optional need M if the ForInterference CSI-ReportConfig identified byreportConfigId is configured with nzp-CSI-RS- ResourcesForInterference;otherwise it is absent.

Table 19 provides an example of aCSI-SemiPersistentOnPUSCH-TriggerStateList IE used to configure the UEwith list of trigger states for semi-persistent reporting of CSI on L1.

TABLE 19 CSI-SemiPersistentOnPUSCH-TriggerStateList information element-- ASN1START -- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STARTCSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE(SIZE(1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerState CSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE {  associatedReportConfigInfo  CSI-ReportConfigId,   ... } --TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP -- ASN1STOP

With respect to the above-described CSI reporting configurations(CSI-ReportConfig), each reporting configuration may be associated witha DL BWP identified by a higher layer parameter BWP identifier (bwp-id)and given by a CSI resource configuration (CSI-ResourceConfig)associated with the each reporting configuration.

As a time domain reporting operation for each reporting configuration,“aperiodic”, “semi-persistent”, and “periodic” types may be supported,and the types may be configured for a terminal by a base station throughthe parameter reportConfigType configured from a higher layer.

A semi-persistent CSI reporting method may support “PUCCH-basedsemi-persistent (semi-PersistentOnPUCCH)”, and “PUSCH-basedsemi-persistent (semi-PersistentOnPUSCH)”. In a periodic orsemi-persistent CSI reporting method, a PUCCH or PUSCH resource on whichCSI is to be transmitted may be configured for a terminal by a basestation through higher layer signaling. The period and slot offset of aPUCCH or PUSCH resource on which CSI is to be transmitted may be givenby the numerology of a UL BWP configured to transmit CSI reporting. Inan aperiodic CSI reporting method, a PUSCH resource on which CSI is tobe transmitted may be scheduled for a terminal by a base station throughL1 signaling (e.g., DCI format 0_1).

With respect to the above-described CSI resource configuration(CSI-ResourceConfig), each CSI resource configuration may include S(where S≥1) pieces of CSI resource sets (e.g., given by a higher layerparameter csi-RS-ResourceSetList). A CSI resource set list may includean NZP CSI-RS resource set and an SS/PBCH block set, or may include aCSI-interference measurement (CSI-IM) resource set. Each CSI resourceconfiguration may be positioned in a DL BWP identified by a higher layerparameter bwp-id and may be connected to a CSI reporting configurationin the same DL BWP. A time domain operation of a CSI-RS resource in aCSI resource configuration may be configured to one of “aperiodic”,“periodic”, or “semi-persistent” by a higher layer parameterresourceType. With respect to a periodic or semi-persistent CSI resourceconfiguration, the number of CSI-RS resource sets may be limited to beS=1, and a configured period and slot offset may be given by thenumerology of a DL BWP identified by a bwp-id. One or more CSI resourceconfigurations for channel and interference measurement may beconfigured for a terminal by a base station through higher layersignaling, and may include the following CSI resources.

-   -   CSI-IM resource for interference measurement    -   NZP CSI-RS resource for interference measurement    -   NZP CSI-RS resource for channel measurement

With respect to CSI-RS resource sets associated with resourceconfigurations having a higher layer parameter resourceType configuredto “aperiodic”, “periodic”, or “semi-persistent”, the trigger state of aCSI reporting configuration having reporType configured to “aperiodic”,and a resource configuration for channel or interference measurement onone or multiple component cells (CCs) may be configured by a higherlayer parameter CSI-AperiodicTriggerStateList.

A terminal may use a PUSCH for aperiodic CSI reporting, and may use aPUCCH for periodic CSI reporting. The terminal may performsemi-persistent CSI reporting using a PUSCH when the reporting istriggered or activated by DCI, and using a PUCCH after the reporting isactivated by a MAC control element (MAC CE).

As described above, a CSI resource configuration may be also configuredto aperiodic, periodic, and semi-persistent. A combination of a CSIreporting configuration and a CSI resource configuration may besupported based on Table 20 below.

TABLE 20 Triggering/Activation of CSI Reporting for the possible CSI-RSConfigurations. CSI-RS Configuration Periodic CSI ReportingSemi-Persistent CSI Reporting Aperiodic CSi Reporting Periodic Nodynamic For reporting on Triggered by DCI; CSI-RS triggering/ PUCCH,theUE additionally, activation receives an activation activation command[10, TS command [10, TS 38.321]; for 38.321] possible as reporting ondefined in Subclause PUSCH, the UE 5.2.1.5.1. receives triggering on DCISemi- Not For reporting on Triggered by DCI; Persistent Supported PUCCH,the UE additionally, CSI-RS receives an activation activation command[10, TS command [10, TS 38.321]; for 38.321] possible as reporting ondefined in Subclause PUSCH, the UE 5.2.1.5.1. receives triggering on DCIAperiodic Not Not Supported Triggered by DCI; CSI-RS Supportedadditionally, activation command [10, TS 38.321] possible as defined inSubclause 5.2.1.5.1.

Aperiodic CSI reporting may be triggered by a “CSI request” field in DCIformat 0_1 described above, corresponding to scheduling DCI of a PUSCH.A terminal may monitor a PDCCH, obtain DCI format 0_1, and obtainscheduling information of a PUSCH and a CSI request indicator. A CSIrequest indicator may be configured to have N_(TS) (=0, 1, 2, 3, 4, 5,or 6) number of bits, and may be determined by higher layer signaling(reportTriggerSize). One trigger state among one or multiple aperiodicCSI reporting trigger states which may be configured by higher layersignaling (CSI-AperiodicTriggerStateList) may be triggered by a CSIrequest indicator.

-   -   if all of the bits in a CSI request field are 0, the bit values        may indicate CSI reporting is not requested.    -   If the number (M) of configured CST trigger states in a        CSI-AperiodicTriggerStateList is larger than 2^(NTs)-1, M CSI        trigger states may be mapped to 2^(NTs)-1 trigger states        according to a pre-defined mapping relation, and one trigger        state among the 2^(NTs)-1 trigger states may be indicated by a        CSI request field.    -   if the number (M) of configured CSI trigger states in a        CSI-AperiodicTriggerStateLite is smaller than or equal to        2^(NTs)-1, one of M CSI trigger states may be indicated by a CST        request field.

Table 21 below shows an example of a relation between a CSI requestindicator and a CSI trigger state that can be indicated by acorresponding indicator.

TABLE 21 CSI request field CSI trigger state CSI- ReportConfigId CSI-ResourceConfigId 00 no CSI request N/A N/A 01 CSI trigger state#1 CSIreport#1 CSI resource#1, CSI report#2 CSI resource#2 10 CSI triggerstate#2 CSI report#3 CSI resource#3 11 CSI trigger state#3 CSI report#4CSI resource#4

A terminal may measure a CSI resource in a CSI trigger state triggeredby a CSI request field, and then generate CSI including at least one ofCQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP described above. The terminalmay transmit obtained CSI by using a PUSCH scheduled by a correspondingDCI format 0_1. If one bit corresponding to a UL data indicator (UL-SCHindicator) in the DCI format 0_1 indicates “1”, the terminal maymultiplex the obtained CSI with UL data (UL-SCH) by using a PUSCHresource scheduled by the DCI format 0_1, to transmit the multiplexedCSI and data. If one bit corresponding to a UL data indicator (UL-SCHindicator) in the DCI format 0_1 indicates “0”, the terminal may maponly the CSI to a PUSCH resource scheduled by the DCI format 0_1,without UL data (UL-SCH), to transmit the CSI.

FIG. 6 illustrates a method of aperiodic CSI measurement and reportingin 5G according to an embodiment.

Referring to FIG. 6 , a terminal may obtain a DCI format 0_1 bymonitoring a PDCCH 601, and obtain scheduling information of a PUSCH 605and CST request information from the DCI format 0_1. The terminal mayobtain resource information of a CSI-RS 602 to be measured, from areceived CSI request indicator. The terminal may determine a time pointat which the terminal should measure a resource of the CSI-RS 602, basedon a time point at which the DCI format 0_1 is received, and anoffset-related parameter (e.g., the aperiodicTriggeringOffset describedabove) in a CSI resource set configuration (e.g., an NZP CSI-RS resourceset configuration (NZP-CSI-RS-ResourceSet)). The terminal may receive anoffset value X of the parameter aperiodicTriggeringOffset in anNZP-CSI-RS resource set configuration from a base station by higherlayer signaling, and the configured offset value X may be an offsetbetween a slot on which DCI triggering aperiodic CSI reporting isreceived, and a slot on which a CSI-RS resource is transmitted. Thevalue of the parameter aperiodicTriggeringOffset and an offset value Xmay have a mapping relation therebetween as shown in Table 22 below.

TABLE 22 aperiodicTriggeringOffset Offset X 0 0 slot 1 1 slot 2  2 slots3  3 slots 4  4 slots 5 16 slots 6 24 slots

In FIG. 6 , an offset value X is configured to be 0. A terminal mayreceive a CSI-RS 602 in slot 0 606 having received a DCI format 01triggering aperiodic CSI reporting. In addition, the terminal may reportCSI information determined based on the received CSI-RS, through thePUSCH 605 to the base station. The terminal may obtain schedulinginformation of the PUSCH 605 for CSI reporting from the DCI format 0_1.For example, the terminal may obtain information associated with a slotin which the PUSCH 605 is to be transmitted, from time domain resourceallocation information of the PUSCH 605, as described above, in the DCIformat 0_1. In FIG. 6 , the terminal obtains 3 as a K2 value 604corresponding to a slot offset value relating to PDCCH-to-PUSCH, andaccordingly, the PUSCH 605 is transmitted in slot 3 609, which is spaced3 slots apart from slot 0 606, i.e., the time point at which the PDCCH601 was received.

FIG. 7 illustrates a method of aperiodic CSI measurement and reportingin 5G according to an embodiment.

Referring to FIG. 7 , a terminal may obtain a DCI format 0_1 bymonitoring a PDCCH 701, and obtain scheduling information of a PUSCH 705and CSI request information from the DCI format 0_1. The terminal mayobtain resource information of a CSI-RS 702 to be measured, from areceived CSI request indicator. In FIG. 7 , an offset value X relatingto a CSI-RS is configured to be 1. A terminal may receive a CSI-RS 702in a slot 707 positioned one slot after slot 1 707 having received a DCIformat 0_1 triggering aperiodic CSI reporting, and may report CSIinformation measured by the received CSI-RS, through a PUSCH 705 to thebase station.

The higher layer signaling may correspond to at least one signalingamong MIB, SIB, RRC, and MAC CE, and L1 signaling may correspond to DCIor PDCCH.

In 5G, one or a plurality of BWPs may be configured for a terminal, andone bandwidth among the configured BWPs may be activated. A base stationmay transmit, to a terminal, a command for activating a particular BWP,after including the command in DCI, and if a BWP index received throughthe DCI is different from the index of a BWP currently activated, theterminal may change the BWP. Since measuring and reporting of a channelstate of an activated BWP can be performed after the BWP is activated,CSI of the activated BWP is absent, and thus, it may be difficult totransmit or receive a data channel immediately after the change to thecorresponding BWP.

In accordance with an aspect of the disclosure, a method is provided formore effectively measuring and reporting a channel state of a changedBWP. If a terminal satisfies a particular condition (e.g., a slot offsetvalue of data scheduling is larger than a particular value, a slotoffset value of CSI measurement is larger than a particular value,etc.), the terminal may change a BWP, measure a reference signaltransmitted in the changed BWP, and transmit a corresponding measurementvalue through the changed BWP. Data transmission or reception in a BWPchanged through the proposed operation can be more effectivelyperformed.

As described above, one or multiple BWPs may be configured for aterminal, and the terminal may perform transmission or reception with abase station through a BWP activated among the one or multiple BWPs. Theterminal may monitor a PDCCH in the activated BWP, and obtain DCI.

The terminal may be instructed to perform aperiodic CSI reporting,through a CSI request field in a DCI (e.g., DCI scheduling PUSCH, or DCIformat 0_1 scheduling PUSCH). A particular code point or a field bitvalue of a CSI request field may indicate a particular CSI trigger state(CSI-AperiodicTriggerState) in a CSI trigger state list(CSI-AperiodicTriggerStateList) configured through higher layersignaling.

A particular CSI trigger state may be associated with a particular CSIreporting configuration (CSI-ReportConfig), and a CSI reportingconfiguration may be associated with the particular CSI resourceconfiguration.

A CSI resource configuration may be associated with one or multiple CSIresource sets (e.g., at least one of NZP CSI-RS resource sets(NZP-CSI-RS-ResourceSet), SSB resource sets (CSI-SSB-ResourceSet), andCSI-IM resource sets (CSI-IM-ResourceSet)).

CSI resource sets in a CSI resource configuration may be associated witha DL BWP, based on the value of a bwp-id or a BWP index-relatedparameter in the CSI resource configuration. If the value of a bwp-id ina particular CSI resource configuration indicates BWP #1, this may implythat CSI resource sets in the CSI resource configuration are positionedin BWP #1. The terminal may perform CSI measurement in a BWP configuredby a bwp-id on CSI resource sets in a CSI resource configurationassociated with a CSI reporting configuration associated with a CSItrigger state indicated by a CSI request field in DCI. The terminal mayreport measured CSI to the base station after mapping the measured CSIto a PUSCH transmission resource scheduled by the received DCI.

There may be an offset between a time point of reception of a DCI formatincluding a CSI request indicator, and a time point of transmission of aCSI resource indicated by the CSI request indicator. The terminal maydetermine a time point at which the terminal should measure a CSI-RStransmitted, based on an offset-related parameter (e.g., anaperiodicTriggeringOffset) in a CSI resource set configuration.

An aperiodic CSI request indicator, a CSI trigger state configuration, aCSI reporting configuration, a CSI resource configuration, and a CSIresource set configuration may be configured for the terminal as shownin Table 23 below.

TABLE 23 CSI CSI request trigger CSI- CSI- NZP-CSI-RS field stateReportConfigId ResourceConfigId ResourceSetConfig 00 no CSI N/A N/A N/Arequest 01 CSI trigger CSI report# CSI resource# NZP-CSI-RSResourceSet#1 state#1 (BWP#1(bwp-id = 1)) (aperiodicTriggering Offset =0) 10 CSI trigger CSI report#2 CSI resource#2 NZP-CSI-RS ResourceSet #2state#2 (BWP#2(bwp-id = 2)) (aperiodicTriggeringOffset = 0) 11 CSItrigger CSI report#3 CSI resource#3 NZP-CSI-RS ResourceSet #3 state#3(BWP#2(bwp-id = 2)) (aperiodicTriggeringOffset = 3)

As shown in Table 23, if the value of a CSI request field is “00”, a CSIrequest is not indicated.

If the terminal receives “01” as the value of a CSI request field, theterminal may measure a CSI-RS received through a CSI resource relatingto CSI resource set configuration #1 (NZP-CSI-RS ResourceSet #1) in CSIresource configuration #1 (CSI resource #1) associated with CSIreporting configuration #1 (CSI report #1). The terminal may generateCSI, based on a result of the measurement, and may report the generatedCSI. CSI resource set configuration #1 may be assumed to be transmittedin BWP #1 according to bwp-id configuration information of CSI resourceconfiguration #1. In addition, the terminal may assume that a slot inwhich DCI is received and a slot in which a CSI-RS is transmitted arethe same, from an offset parameter in a CSI resource set configuration(aperiodicTriggeringOffset=0).

If the terminal receives “10” as the value of a CSI request field, theterminal may measure a CSI-RS received through a CSI resource relatingto CSI resource set configuration #2 (NZP-CSI-RS ResourceSet #2) in CSTresource configuration #2 (CSI resource #2) associated with CSIreporting configuration #2 (CSI report #2). The terminal may generateCSI, based on a result of the measurement, and may report the generatedCSI. CSI resource set configuration #2 may be assumed to be transmittedin BWP #2 according to bwp-id configuration information of CSI resourceconfiguration #2. In addition, the terminal may assume that a slot inwhich DCI is received and a slot in which a CSI-RS is transmitted arethe same, from an offset parameter in a CSI resource set configuration(aperiodicTriggeringOffset=0).

If the terminal receives “11” as the value of a CSI request field, theterminal may measure a CSI-RS received through a CSI resource relatingto CSI resource set configuration #3 (NZP-CSI-RS ResourceSet #3) in CSIresource configuration #3 (CSI resource #3) associated with CSIreporting configuration #3 (CSI report #3). The terminal may generateCSI, based on a result of the measurement, and may report the generatedCSI. CSI resource set configuration #3 may be assumed to be transmittedin BWP #2 according to bwp-id configuration information of CSI resourceconfiguration #3. In addition, the terminal may measure a CSI-RS andgenerate CSI by assuming, from an offset parameter in a CSI resource setconfiguration, that a slot in which the CSI-RS is transmitted is slotn+3 if a slot having received DCI is slot n(aperiodicTriggeringOffset=3).

In a method for performing aperiodic CSI measurement and reporting, aBWP that has been currently activated, a BWP indicated by a BWPindicator of DCI, and a BWP in which a CSI-RS indicated by a CSI requestindicator is transmitted may be identically or differently indicated.According to the contents of an indicator, the terminal may perform CSImeasurement and reporting on a current BWP, or may perform CSImeasurement and reporting on a changed BWP.

Various embodiments related to a method for CSI measurement andreporting in consideration of a BWP change are proposed.

For convenience, some terms used below will be defined as follows.

BWP A: a BWP that has been activated

BWP B: a BWP indicated by a BWP indicator (or a BWP in which a datachannel (e.g., a PUSCH) is scheduled)

BWP C: a BWP in which a CSI resource indicated by a CSI requestindicator is transmitted

If BWP A, BWP B, and BWP C are all the same (e.g. BWP A=BWP B=BWP C =BWP#1), the terminal may measure a CSI-RS in a currently activated BWP #1,generate CSI, and report the measured CSI to the base station in BWP #1by using a PUSCH scheduled by received DCI.

If both BWP A and BWP C are the same, but BWP B is different (e.g., BWPA=BWP C(=BWP #1) #BWP B (=BWP #2)), the terminal may measure a CSI-RS incurrently activated BWP #1, generate CSI, perform a BWP change to BWP #2indicated by received DCI, and report the CSI measured in BWP #1 to thebase station in BWP #2 by using a PUSCH.

If BWP A and BWP B are the same, but BWP C is different (e.g., BWP A=BWPB (=BWP #1) BWP C(=BWP #2)), or BWP A, BWP B, and BWP C are alldifferent from each other (e.g., BWP A (=BWP #1): BWP B (=BWP #2) #BWPC(=BWP #3)), the terminal may determine there is an error in receivedDCI. That is, the terminal may not expect triggering of aperiodic CSIreporting with respect to a BWP that is different from a currentlyactivated BWP, or a BWP of a data channel (e.g., a PUSCH) scheduled byDCI.

If BWP B and BWP C are the same, but BWP A is different (e.g. BWP A(=BWP #1) t BWP B=BWP C(=BWP #2)), the terminal may perform a BWP changeand perform CSI measurement and reporting on the changed BWP. Theterminal may receive and measure a CSI-RS transmitted in the changedBWP, and report CSI measured in the changed BWP to the base station byusing a PUSCH scheduled by received DCI.

The terminal may assume that a time point at which the CSI-RS istransmitted in the changed BWP corresponds to a slot in which the PUSCHis transmitted. That is, the terminal may assume that an offset value(e.g., an aperiodicTriggeringOffset) between a time point at which a DCIformat including a CSI request indicator is received and a time point atwhich a CSI resource indicated by the CSI request indicator istransmitted corresponds to a K2 value in time domain resource allocationinformation of a PUSCH scheduled by corresponding DCI.

FIG. 8 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment.

Referring to FIG. 8 , BWP #1 810 and BWP #2 820 are configured for aterminal. If a current time point corresponds to slot 0 806, BWP #1 810is an activated BWP, and the terminal may monitor a PDCCH 801 in BWP #1810 to obtain DCI.

The terminal may obtain scheduling information of a PUSCH 805, a BWPindicator, and a CSI request indicator from the received DCI. In FIG. 8, a BWP indicator included in DCI is assumed to indicate BWP #2 820, anda CSI request indicator is assumed to indicate a CSI-RS resource set ofBWP #2 820 (i.e., the CSI request indicator indicates a CSI triggerstate associated with a CSI reporting configuration associated with aCSI resource configuration configured to bwp-id=2, e.g., the CSI requestindicator may correspond to a CSI request field of “11” in Table 23above).

The terminal may perform a BWP change from BWP #1 810 to BWP #2 820according to a command of a BWP indicator in the received DCI. Theterminal may expect that the terminal does not perform any transmissionor reception during T 830, which is a time interval from a third symbolof a slot in which a PDCCH 801 having obtained DCI is transmitted, to astarting point of a slot in which a PUSCH 805 is scheduled. The startingpoint of the slot in which the PUSCH 805 is scheduled may be determinedby the value of a K2 804 in time domain resource allocation informationof the PUSCH 805.

The terminal may perform transmission or reception in BWP #2 820 fromslot 3 809, based on the value of the K2 804 indicated by the DCI. Theterminal may assume that a CSI-RS of BWP #2 820 is transmitted at a timepoint at which the PUSCH 805 is transmitted (i.e., slot 3 809), and maymeasure the CSI-RS 802. That is, the terminal may assume that a resourceoffset 803 of the CSI-RS is identical to the K2 804.

To determine a transmission time point of a CSI-RS, at least one Methods1 to 3 below, or a combination thereof, may be used.

Method 1

The terminal may neglect an offset-related parameter field value (e.g.,aperiodicTriggeringOffset) in a CSI resource set configuration indicatedby a CSI request indicator, and may assume that the field value is thesame as K2.

Method 2

The terminal may expect that CSI reporting on a CSI resource set inwhich an offset-related parameter value (e.g.,aperiodicTriggeringOffset) in a CSI resource set configuration indicatedby a CSI request indicator is the same as K2 is to be triggered. Thatis, if the base station requests CSI measurement and reporting on achanged BWP from the terminal, the base station may indicate a CSItrigger state associated with a CSI resource set having the same offsetvalue as K2 by using a CSI request indicator.

Method 3

The terminal may expect that a K2 value indicated by a time domainresource allocation indicator of a PUSCH is indicated to be the same asan offset-related parameter value in a CSI resource set configurationindicated by a CSI request indicator. That is, if the base stationrequests CSI measurement and reporting on a new BWP from the terminal byusing a CSI request indicator, the base station may indicate a K2 valuerelating to a PUSCH such that the K2 value is the same as an offsetvalue in a CSI resource set triggered by the CSI request indicator.

As described above, a terminal can perform CSI measurement and reportingon a changed BWP as fast as possible. That is, CSI measurement andreporting can be performed immediately after a BWP change. Accordingly,a base station can quickly obtain CSI relating to a changed BWP from aterminal, and effectively perform data transmission or reception in thechanged BWP, based on the obtained CSI.

A terminal immediately performs CSI measurement and reporting on achanged BWP, so that the terminal can quickly complete variouspreparation processes (e.g., channel measurement, time and frequencytracking, adaptive gain control (AGC), etc.) for transmitting orreceiving data in the changed BWP, and can effectively transmit orreceive data. In addition, additional activation time for channelmeasurement and reporting of a terminal is minimized, so that the powerconsumption of the terminal can be reduced.

If the terminal receives scheduling information of a PUSCH excluding ULdata (UL-SCH) by a UL data indicator (e.g., a UL-SCH indicator) field inDCI (i.e., one bit corresponding to the UL-SCH indicator indicates “0”),the terminal may apply the method illustrated in FIG. 8 . That is, if aPUSCH only for CSI reporting, not for the purpose of transmitting ULdata, is scheduled for the terminal from the base station, the terminalmay exceptionally perform the above described method for CSI measurementand reporting on a new BWP.

If a K2 value in time domain resource allocation information of a PUSCHin DCI is larger than a particular threshold (9), the terminal may applythe method illustrated in FIG. 8 . If a K2 value is larger, the terminalmay sufficiently ensure time for preparations for a change to a new BWP,CSI measurement in the new BWP, and PUSCH transmission in the new BWP,and thus it may be easier for the terminal to perform CSI measurementand reporting on a new BWP as described above. Therefore, if a K2 valueis larger than a threshold, the terminal may exceptionally perform theabove described method for CSI measurement and reporting on a new BWP.

If BWP B and BWP C are the same, BWP A is different (e.g., BWP A (=BWP#1) ≠BWP B=BWP C(=BWP #2)), and a CSI resource offset value indicated bya CSI request indicator in obtained DCI is larger than a BWP changelatency time interval of the terminal (e.g., T_(BWP)), the terminal mayperform a BWP change and perform CSI measurement and reporting on achanged BWP.

More specifically, the terminal may perform a BWP change according to aBWP indicator and generate CSI by measuring a CSI resource relating to achanged BWP at a time point after T_(BWP), as specified by a CSIresource offset.

The terminal may report the generated CSI at a time point oftransmission of a PUSCH scheduled by corresponding DCI. The time pointmay be indicated by a time domain resource allocation field. The CSIresource offset value indicated by the CSI request indicator in the DCImay be indicated to be larger than T_(BWP) and smaller than or equal toa K2 value in time domain resource allocation information of the PUSCH.

FIG. 9 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment.

Referring to FIG. 9 , BWP #1 910 and BWP #2 920 are configured for aterminal. If a current time point corresponds to slot 0 906, BWP #1 910is an activated BWP, and the terminal may monitor a PDCCH 901 in BWP #1910 to obtain DCI. The terminal may obtain scheduling information of aPUSCH 905, a BWP indicator, and a CSI request indicator from thereceived DCI.

In FIG. 9 , a BWP indicator included in DCI is assumed to indicate BWP#2 920, and a CSI request indicator is assumed to indicate a CSI-RSresource set of BWP #2 920 (i.e., the CSI request indicator indicates aCSI trigger state associated with a CSI reporting configurationassociated with a CSI resource configuration configured to bwp-id=2,e.g., the CSI request indicator may correspond to a CSI request field of“11” as shown in Table 23 above).

In FIG. 9 , a BWP change latency time interval T_(BWP) of the terminalis assumed to be one slot, an offset value (e.g., anaperiodicTriggeringOffset) of a CSI resource indicated by a CSI requestindicator in DCI is assumed to be 2, and a scheduling offset value (K2)of the PUSCH 905 is assumed to be 3. That is, a situation in which anoffset value of a CSI resource indicated by a CSI request indicator islarger than T_(B)WP and equal to or smaller than a K2 value is assumed.

The terminal may perform a BWP change from BWP #1 910 to BWP #2 920according to a BWP indicator in the received DCI. The terminal mayexpect that the terminal does not perform any transmission or receptionduring T 930, which is a time interval from a third symbol of a slot 906in which a PDCCH 901 having obtained DCI was transmitted to a startingpoint of a slot in which a PUSCH 905 is scheduled. The starting pointmay be determined by the value of a K2 904 in time domain resourceallocation information of the PUSCH 905.

If an offset value of a CSI resource indicated by a CSI requestindicator in DCI is larger than T_(BWP), the terminal may only receive aCSI-RS 902 in a changed BWP (e.g., BWP #2 920 in FIG. 9 ) at acorresponding CSI-RS transmission time point. That is, in FIG. 9 , theterminal may not perform transmission or reception, except for receivingthe CSI-RS 902 in BWP #2 920 at the time point of slot 2 908, during atime interval T 930.

The terminal may generate CSI based on the CST-RS 902 received in BWP #2920 at the time point of slot 2 908, and report the generated CSIthrough the PUSCH 905 (i.e., PUSCH scheduled by obtained DCI) of slot 3909 to the base station.

As described above, a terminal can perform CSI measurement and reportingon a changed BWP quicker than a conventional terminal. Moreover, thereis a difference between a CSI measurement time point and a CSI reportingtime point, and thus a terminal can ensure the time required to reportCSI in UL after measuring and generating the CSI in DL. Accordingly, abase station can quickly obtain CSI relating to a changed BWP from aterminal, and effectively perform data transmission or reception in thenew BWP, based on the obtained CSI.

A terminal immediately performs CSI measurement and reporting on achanged BWP, so that the terminal can quickly complete variouspreparation processes (e.g., channel measurement, time and frequencytracking, AGC, etc.) for transmitting or receiving data in the changedBWP, and can effectively transmit or receive data. In addition,additional activation time for channel measurement and reporting of aterminal is minimized, so that the power consumption of the terminal canbe reduced.

If the terminal receives scheduling information of a PUSCH excluding ULdata (e.g., UL-SCH) by a UL data indicator (e.g., UL-SCH indicator)field in DCI (i.e., one bit corresponding to the UL-SCH indicatorindicates “0”), the terminal may perform the method illustrated in FIG.9 . That is, if a PUSCH only for CSI reporting, not for the purpose oftransmitting UL data, is scheduled for the terminal from the basestation, the terminal may perform the above described method for onlyCSI measurement and reporting on a new BWP.

If a K2 value in time domain resource allocation information of a PUSCHin DCI is larger than a particular threshold (η), the terminal mayperform the method illustrated in FIG. 9 . If a K2 value is larger, theterminal may sufficiently ensure time for preparations for a change to anew BWP, CSI measurement in the new BWP, and PUSCH transmission in thenew BWP, and thus it may be easier for the terminal to perform CSImeasurement and reporting on a new BWP as described above. Therefore, ifa K2 value is larger than a particular threshold, the terminal mayperform the above described method only for CSI measurement andreporting on a new BWP.

In accordance with an aspect of the disclosure, a method for measuringand reporting CSI by using scheduling DCI (e.g. DCI format 1_1) of aPDSCH is provide, wherein a base station may indicate, to a terminal,scheduling information of a PDSCH, and allocation information (e.g., aPUCCH resource indicator in DCI format 1_1) of a PUCCH in which aHARQ-ACK for the PDSCH is to be transmitted, by using DCL. Specifically,the base station may indicate, to the terminal, a K0 value as a part oftime domain resource allocation information of a PDSCH, a PUCCH resourceon which an HARQ-ACK for the PDSCH is transmitted, and a K1 valuecorresponding to a time point at which the PUCCH resource istransmitted.

A K0 value may correspond to PDCCH-to-PDSCH slot timing as describedabove, i.e., a time interval in units of slots between a time point ofreception of a PDCCH and a time point of transmission of a PDSCHscheduled by the received PDCCH, and a K1 value may correspond toPDSCH-to-PUCCH slot timing, i.e., a time interval in units of slotsbetween a time point of reception of a PDSCH and a time point oftransmission of a HARQ-ACK for the received PDSCH. A K1 value is one ofconfiguration parameters relating to a PUCCH, and may be configured fora terminal by a base station through higher layer signaling (e.g., RRC).The PUCCH configuration information may include the parameters as shownin Table 24 below.

TABLE 24 PUCCH-Config information element -- ASNISTART --TAG-PUCCH-CONFIG-START PUCCH-Config ::= SEQUENCE {  resourceSetToAddModList  SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet  OPTIONAL, -- Need N  resourceSetToReleaseList  SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId  OPTIONAL, -- Need N  resourceToAddModList  SEQUENCE (SIZE (1..maxNrotPUCCH- Resources)) OFPUCCH-Resource  OPTIONAL, -- Need N   resourceToReleaseList  SEQUENCE(SIZE (1..maxNrofPUCCH- Resources)) OF PUCCH-ResourceId  OPTIONAL, --Need N   format1 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M  format2 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M  format3 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M  format4 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M  schedulingRequestResourceToAddModList     SEQUENCE (SIZE(1..maxNrofSR- Resources)) OFSchedulingRequestResourceConfig    OPTIONAL, -- Need N  schedulingRequestResourceToReleaseList     SEQUENCE (SIZE(1..maxNrofSR- Resources)) OF SchedulingRequestResourceId     OPTIONAL,-- Need N   multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OFPUCCH- ResourceId OPTIONAL, -- Need M   dl-DataToUL-ACK SEQUENCE (SIZE(1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M  spatialRelationInfoToAddModList SEQUENCE (SIZE(1..maxNrofSpatialRelationInfos))  OF  PUCCH-SpatialRelationInfo  OPTIONAL, --Need N   spatialRelationInfoToReleaseList SEQUENCE (SIZE(1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoIdOPTIONAL, -- Need N   pucchPowerControl PUCCH-PowerControl OPTIONAL, --Need M   ... }

The parameter dl-DataToUL-ACK among the parameters relating to a PUCCHconfiguration may correspond to a K1 value, and may be 0 to 15. That is,the base station may indicate, to the terminal, a PUCCH resource amongmultiple PUCCH resources configured through higher layer signaling, as aPUCCH resource on which a HARQ-ACK for a PDSCH is to be transmitted, byusing a PUCCH resource indicator in DCI, and the base station mayidentify a K1 value that is information relating to a timing at whichthe PUCCH is to be transmitted, from the parameter dl-DataToUL-ACK inconfiguration information of the PUCCH resource indicated to theterminal.

The base station may trigger aperiodic CSI reporting for the terminal byDCI scheduling a PDSCH, and the terminal may report corresponding CSI byusing a PUCCH resource indicated by a PUCCH resource indicator in theDCI.

FIG. 10 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment.

Referring to FIG. 10 , BWP #1 1010 and BWP #2 1020 are configured for aterminal. If a current time point corresponds to slot 0 1006, BWP #11010 is an activated BWP, and the terminal may monitor a PDCCH 1001 inBWP #1 1010 to obtain DCI. The terminal may obtain schedulinginformation of a PUSCH 1011, resource information of a PUCCH 1005, a BWPindicator, and a CSI request indicator from the received DCI.

In FIG. 10 , a BWP indicator included in DCI is assumed to indicate BWP#2 1020, and thus the PDSCH 1011 may be scheduled to BWP #2 1020 to betransmitted. In addition, a CSI request indicator is assumed to indicatea CSI-RS resource set of BWP #2 1020.

The terminal may perform a BWP change from BWP #1 1010 to BWP #2 1020according to a BWP indicator in the received DCI. The terminal mayexpect that the terminal does not perform any transmission or receptionduring T 1030, which is a time interval from a third symbol of a slot1006 in which a PDCCH 1001 having obtained DCI is transmitted to astarting point of a slot in which a PDSCH 1011 is scheduled. Thestarting point may be determined by the value of a K0 1004 in timedomain resource allocation information of the PDSCH 1011.

The terminal may perform transmission or reception in BWP #2 1020 fromslot 2 1008, based on the value of the K0 1004 indicated by the DCI.FIG. 10 illustrates an example in which the terminal performs a BWPchange and then receives data through the PDSCH 1011 in BWP #2 1020(i.e., the CSI request indicator indicates a CSI trigger stateassociated with a CSI reporting configuration associated with a CSIresource configuration configured to bwp-id=2, and for example, the CSIrequest indicator may correspond to a CSI request field of “11” in table23).

The terminal may assume that a CSI-RS of BWP #2 1020 is transmitted at atime point at which the PDSCH 1011 is transmitted (i.e., slot 2 1008),and may measure the CSI-RS. That is, the terminal may assume that aresource offset 1003 of the CSI-RS corresponds to the K0 1004.

To determine a transmission time point of a CSI-RS, at least one ofMethods 1 to 3 below, or a combination thereof, may be used.

Method 1

The terminal may neglect an offset-related parameter field value (e.g.,aperiodicTriggeringOffset) in a CSI resource set configuration indicatedby a CSI request indicator, and may assume that the field value is thesame as K0.

Method 2

The terminal may expect that CSI reporting on a CSI resource set inwhich an offset-related parameter (value in a CSI resource setconfiguration indicated by a CSI request indicator is the same as K0 isto be triggered. That is, if the base station is to request CSImeasurement and reporting on a changed BWP from the terminal, the basestation may indicate a CSI trigger state associated with a CSI resourceset having the same offset value as K0 by using a CSI request indicator.

Method 3

The terminal may expect that a K0 value indicated by a time domainresource allocation indicator of a PDSCH is indicated to be the same asan offset value in a CSI resource set configuration indicated by a CSIrequest indicator. That is, if the base station requests CSI measurementand reporting on a new BWP from the terminal by using a CSI requestindicator, the base station may indicate a K2 value relating to a PDSCH,such that the K2 value is the same as an offset value in a CSI resourceset triggered by the CSI request indicator.

A resource for a PUCCH 1005 through which an HARQ-ACK for the PDSCH 1011is to be transmitted may be allocated to the terminal by a PUCCHresource indicator in the received DCI. The base station may identifythe value of a K1 1013 that is information relating to a timing at whichthe PUCCH 1005 is to be transmitted, from the parameter dl-DataToUL-ACKin a resource configuration of the PUCCH 1005, indicated by the PUCCHresource indicator.

In FIG. 10 , the value of the K1 1013 is assumed to be one slot, andaccordingly, the terminal may transmit, through the PUCCH 1005, HARQ-ACKinformation relating to the PDSCH 1011 received in slot 2 1008, in slot3 1009 positioned as much as the K1 1013, i.e., one slot later than slot2. The terminal may multiplex CSI measured by using a CSI-RS 1002received in slot 2 1008, with the HARQ-ACK information relating to thePDSCH 1011, and then transmit the multiplexed CSI and informationthrough the PUCCH 1005 in slot 3 1009. As a HARQ-ACK on the PDSCH 1011and the CSI are multiplexed, the size of uplink control information(UCI) transmitted through the PUCCH 1005 may be changed, and theterminal may reselect a resource of the PUCCH 1005 to be transmitted inslot 3 1009, based on a predefined series of methods.

As described above, a terminal can perform CSI measurement and reportingon a changed BWP as fast as possible. An aperiodic CSI request isindicated by using DCI scheduling a PDSCH, whereby there is a differencebetween a CSI measurement time point and a CSI reporting time point, andthus a terminal can ensure the time required to report CSI in UL aftermeasuring and generating the CSI in DL. A base station can quicklyobtain CSI relating to a changed BWP from a terminal, and effectivelyperform data transmission or reception in the changed BWP, based on theobtained CSI.

A terminal immediately performs CSI measurement and reporting on achanged BWP, so that the terminal can quickly complete variouspreparation processes (e.g., channel measurement, time and frequencytracking, AGC, etc.) for transmitting or receiving data in the changedBWP, and can effectively transmit or receive data. In addition,additional activation time for channel measurement and reporting of aterminal is minimized, so that the power consumption of the terminal canbe reduced.

As described above, DL data indicator (e.g., a DL-SCH indicator) may beincluded in a DCI format indicating an aperiodic CSI request. If one bitcorresponding to a DL data indicator in a DCI format indicates “1”, thismay indicate that a DL-SCH exists in a PDSCH scheduled by the DCIformat. If one bit corresponding to the DL data indicator in a DCIformat indicates “0”, this may indicate that no DL-SCH exists in a PDSCHscheduled by the DCI format.

If aperiodic CSI reporting has been triggered by a CSI request indicatorin DCI, and the DL data indicator indicates “1”, the terminal maymultiplex CSI with an HARQ-ACK for the DL-SCH by using a PUCCH resourceindicated by the DCI, and then report the multiplexed CSI and HARQ-ACKto the base station.

If aperiodic CSI reporting has been triggered by a CSI request indicatorin DCI, and the DL data indicator indicates “0”, the terminal may mapCSI to a PUCCH resource indicated by the DCI, and then report the mappedCSI to the base station. That is, aperiodic CSI reporting can betriggered by using a DL data indicator, without scheduling actual DLdata.

If the terminal receives scheduling information of a PDSCH excluding DLdata (e.g., a DL-SCH) through a DL data indicator (e.g., a DL-SCHindicator) field in DCI (i.e., one bit corresponding to the DL-SCHindicator indicates “0”), the terminal may apply the method illustratedin FIG. 10 . That is, if a PDSCH only for CSI reporting, not for thepurpose of transmitting DL data, is scheduled for the terminal from thebase station, the terminal may perform the above described method foronly CSI measurement and reporting on a new BWP. The terminal may reportmeasured CSI to the base station after mapping the measured CSI to aPUCCH resource indicated by a PUCCH resource indicator in DCI.

If a K0 value in time domain resource allocation information of a PDSCHin DCI is larger than a particular threshold (9), the terminal may applythe method illustrated in FIG. 10 . If a K0 value is larger, theterminal may sufficiently ensure time for preparations for a change to anew BWP, CSI measurement in the new BWP, and PUCCH transmission in thenew BWP, and thus it may be easier for the terminal to perform CSImeasurement and reporting on a new BWP. Therefore, if a K0 value islarger than a particular threshold, the terminal may perform the abovedescribed method for only CSI measurement and reporting on a new BWP.

The above-described embodiments may also be applied to TDD.

The above-described embodiments may be carried out in combination.

The above-described various embodiments may be applied to a single cellenvironment or a multi-cell environment (e.g., a carrier aggregation(CA)).

If one or more BWPs are configured for a terminal, a base station mayinstruct the terminal to change a BWP, by using a BWP indicator field inthe DCI. For FDD, change of a UL BWP may be indicated by DCI (e.g., DCIformat 0_1) scheduling a PUSCH, and change of a DL BWP may be indicatedby DCI (e.g., DCI format 1_1) scheduling a PDSCH.

For convenience, some of the terms used below will be defined asfollows.

-   -   DL DCI: DCI scheduling PDSCH    -   UL DCI: DCI scheduling PUSCH    -   BWP A_(DL): a DL BWP which is currently activated    -   BWP A_(UL): a UL BWP which is currently activated    -   BWP B_(DL): a BWP indicated by a BWP indicator in DL DCI (or a        BWP in which a PDSCH is scheduled)    -   BWP B_(UL): a BWP indicated by a BWP indicator in UL DCI (or a        BWP in which a PUSCH is scheduled)    -   BWP C: a DL BWP configured for a CSI resource indicated by a CSI        request indicator in UL DCI (or a DL BWP in which a        corresponding CSI-RS is transmitted)

In an operation according to FDD, in accordance with an aspect of thedisclosure, a method is provided for measuring and reporting CSIrelating to a changed DL BWP after a BWP change.

In relation to FDD, if a currently activated DL BWP (BWP A_(DL)) and aBWP (BWP C) in which a CSI-RS resource indicated by a CSI requestindicator in UL DCI is transmitted are different (i.e., BWP A_(DL)≠BWPC), the terminal may change a DL BWP to BWP C, receive a CSI-RS in thechanged BWP, and report the CSI-RS to the base station through a PUSCHscheduled by the UL DCI.

FIG. 11 illustrates a method of aperiodic CSI measurement and reportingaccording to an embodiment.

Referring to FIG. 11 , DL BWP #1 1110 and DL BWP #2 1120, and UL BWP #11121 are configured for a terminal. If a current time point correspondsto slot 0 1106, DL BWP #1 1110 is an activated DL BWP, and the terminalmay monitor a PDCCH 1101 in DL BWP #1 1110 to obtain DCI. The terminalmay obtain scheduling information of a PUSCH 1105, a UL BWP indicator,and a CSI request indicator from the received DCI.

In FIG. 11 , a UL BWP indicator included in DCI may indicate a currentlyactivated UL BWP #1 1121, or a UL BWP indicator is not included in DCIbecause the number of UL BWPs configured for the terminal is one. Thatis, in FIG. 11 , it is assumed that the PUSCH 1105 scheduled by the ULDCI is transmitted in a currently activated UL BWP, i.e., UL BWP #11121.

If a plurality of UL BWPs are configured for the terminal, it is alsopossible to change a UL BWP to a BWP indicated by a UL BWP indicator inUL DCI, and then transmit a PUSCH in the changed UL BWP.

In FIG. 11 , a CSI request indicator in UL DCI received by the terminalis assumed to indicate a CSI-RS resource set of DL BWP #2 1120 (e.g.,the CSI request indicator indicates a CSI trigger state associated witha CST reporting configuration associated with a CST resourceconfiguration configured to bwp-id=2, and for example, the CSI requestindicator may correspond to a CSI request field of “11” in table 23).That is, DL BWP #1 1110, which is a currently activated DL BWP, and DLBWP #2 1120, which is a DL BWP configured for a CST resource indicatedby a CST request indicator in UL DCI, may be indicated differently.

The terminal may perform a BWP change to DL BWP #2 1120 that is a DL BWPconfigured for a CSI resource indicated by a CSI request indicator inreceived UL DCI. The value of an offset 1103 of the CSI resourceindicated by the CSI request indicator in the UL DCI may be indicated tobe larger than T_(BWP) 1140 in consideration of T_(BWP) that is a BWPchange latency time interval. In FIG. 11 , a BWP change latency timeinterval T_(B)WP of the terminal is assumed to be one slot, an offsetvalue 1103 (e.g., aperiodicTriggeringOffset) of a CSI resource indicatedby a CSI request indicator in DCI is assumed to be 2, and a schedulingoffset value (K2 1104) of the PUSCH 1105 is assumed to be 3.

The terminal may expect that it does not perform any transmission orreception during T 1130, which is a time interval from a third symbol ofa slot 1106 in which a PDCCH 1101 having obtained UL DCI is transmittedto a starting point of a slot in which a CSI-RS 1102 is transmitted. Thestarting point may be determined by the offset 1103 of the CSI resource.The terminal may perform transmission or reception in DL BWP #2 1120from slot 2 1109, based on the value of the offset 1103 of the CSIresource indicated by the UL DCI. The terminal may receive the CSI-RS1102 transmitted in DL BWP #2 1120, in slot 2 1108, and measure andgenerate CSI. The terminal may report the measured CSI through the PUSCH1105 (i.e., PUSCH scheduled by obtained UL DCI) of slot 3 1109 to thebase station.

As described above, a terminal can perform CSI measurement and reportingon a changed DL BWP as fast and effectively as possible in an FDDenvironment. A DL BWP changing function (i.e., a change to a DL BWP inwhich a CSI-RS is transmitted) is also supported as well as an aperiodicCSI request by UL DCI, and thus DL DCI scheduling a PDSCH to change a DLBWP in FDD may not be required to be additionally transmitted. A basestation can quickly obtain CSI relating to a new BWP from a terminal,and effectively perform data transmission or reception in the new BWP,based on the obtained CSI.

In accordance with the above-described embodiments, a terminal moreefficiently performs CSI measurement and reporting on a changed BWP, sothat the terminal can quickly complete various preparation processes(e.g., channel measurement, time and frequency tracking, AGC, etc.) fortransmitting or receiving data in the changed BWP, and can effectivelytransmit or receive data. In addition, additional activation time forchannel measurement and reporting of a terminal is minimized, reducingthe power consumption of the terminal.

The above-described embodiments may be applied to a case of FDD.However, the disclosure is not limited thereto, and the secondembodiment may also be applied to a case of TDD.

The above-described embodiments may be carried out in combination.

The above-described embodiments may be partially applied to a singlecell environment or a multi-cell environment (e.g., CA).

As described above, field values (or code points) of a CSI requestindicator may be associated with CSI trigger states, and each CSItrigger state may be associated with a CSI reporting configuration and aCSI resource configuration. A CSI reporting configuration may beconfigured to be associated with a particular cell through a cell indexparameter (e.g., ServCellIndex), and a CSI resource configuration may beassociated with a particular BWP through a BWP index parameter (e.g.,bwp-id). A terminal may obtain DCI, and then generate CSI by measuring aCSI resource transmitted in a BWP corresponding to a BWP index in a CSIresource configuration, in a cell corresponding to a cell index in a CSIreporting configuration indicated by a CSI request indicator in the DCI.The terminal may report the generated CSI to a base station by using aPUSCH scheduled by the DCI.

Table 25 below shows an example of a CSI request indicator. In Table 25,one CSI request indicator value may be associated with (or may indicate)multiple CSI reporting configurations and multiple CSI resourceconfigurations. Cell indices in the multiple CSC reportingconfigurations associated with the one CSI request indicator value maybe identical or different. In addition, bandwidth part indices in themultiple CSI resource configurations associated with the one CSI requestindicator value may be identical or different.

TABLE 25 CSI request CSI trigger CSI- CSI- field state ReportConfigIdResourceConfigId 00 no CSI request N/A N/A 01 CSI trigger state#1 CSIreport# CSI resource#1, (ServCellIndex = 1) (bwp-id = 1) CSI report#2CSI resource#2 (ServCellIndex = 1) (bwp-id = 2) 10 CSI trigger state#2CSI report#3 CSI resource#3 (ServCellIndex = 2) (bwp-id = 1) CSIreport#4 CSI resource#4 (ServCellIndex = 3) (bwp-id = 1) 11 CSI triggerstate#3 CSI report#5 CSI resource#5 (ServCellIndex = 4) (bwp-id = 1) CSIreport# CSI resource#6 (ServCellIndex = 5) (bwp-id = 2)

The terminal may not expect that aperiodic CSI reporting is triggeredwith respect to a BWP that is not currently activated. Only one BWP canbe activated in one cell, and thus a case where a field value of aparticular CSI request indicator is associated with CSI resourceconfigurations relating to different BWPs in the same cell may beproblematic.

In accordance with an aspect of the disclosure, different methods forsolving the problem are provided below.

Method 1

If a terminal obtains a CSI request indicator associated with CSIresource configurations of different BWPs in the same cell, the terminalmay measure, in the CSI resource configurations indicated by the CSIrequest indicator, a CSI resource configured to have a BWP indexidentical to a currently activated BWP, and neglect information relatingto a CSI resource configured to have a BWP index different from thecurrently activated BWP.

For example, if the terminal receives “01” as a CSI request indicator,as shown in Table 25 above, and a currently activated BWP is BWP #1, theterminal may measure only CSI resource #1 configured to have bwp-id of1, and may not measure CSI resource #2 configured to have bwp-id of 2.The terminal may report CSI generated based on the measurement of theCSI resource, to a base station.

Method 2

A terminal may not expect that one CSI request indicator field value isconfigured to be associated with multiple CSI resources in differentBWPs in the same cell. That is, one CSI request indicator field valuemay be associated with only CSI resources in the same BWP in the samecell. For example, the terminal may not expect an associationconfiguration such as CSI reporting and resource configurationscorresponding to a CSI request indicator field value of “01”, as shownin Table 25.

Method 3

A terminal may not expect receiving of a CSI request indicator fieldvalue associated with multiple CSI resources in different BWPs in thesame cell. For example, the terminal may not expect receiving of a CSIrequest indicator field value of “01”, as shown in Table 25.

A CSI-RS may have a quasi-co-located (QCL) relationship with other RSs.In 5G, the four QCL types may be supported as below.

-   -   “QCL-Type A”: (Doppler shift, Doppler spread, average delay,        delay spread)    -   “QCL-Type B”: {Doppler shift, Doppler spread}    -   “QCL-Type C”: {Doppler shift, average delay}    -   “QCL-Type D”: (Spatial Rx parameter (antenna reception        parameter))

Some RSs may be quasi-co-located in at least one QCL type among the QCLtypes, and a terminal may assume that RSs quasi-co-located in aparticular QCL type have the same parameters defined by the QCL type.

With respect to aperiodic CSI reporting, an offset of a CSI-RS (e.g.,aperiodicTriggeringOffset) may be configured by higher layer signaling.The terminal may receive a CSI-RS at a time point considering an offsetin a CSI resource set configuration indicated by a CSI requestindicator, and generate CSI.

If all of the CSI-RSs in a CSI trigger state, which are associated witheach other, are not configured in a QCL-TypeD (i.e., a higher layerparameter qcl-Type is not configured to be “QCL-TypeD”), an offset valueof a CSI-RS may be fixed to 0. For example, if a communication frequencyband corresponds to low frequency (e.g., a frequency range 1 (FR 1), ora frequency band of 6 GHz or lower), the band may not support QCL-TypeD,and thus an offset value of a CSI-RS may be fixed to 0. If acommunication frequency band corresponds to high frequency (e.g.,frequency range 2 (FR 2), or a frequency band of 6 GHz or higher),QCL-TypeD may be configured, and thus an offset value of a CSI-RS may beconfigured to be larger than 0.

The terminal may identify, based on a K0 (or K2) value in a time domainresource allocation information for a PDSCH (or a PUSCH), the positionof a slot in which the corresponding data channel is scheduled. If theterminal receives a PDCCH scheduling a PDSCH, in slot n, and receives K0of 0, this may indicate that the PDSCH is scheduled in slot n. Ascenario in which a control channel and a data channel are scheduled inthe same slot, i.e., a slot offset value (K0, K2) is 0, may be referredto as “self-slot scheduling”.

As another example, if the terminal receives a PDCCH scheduling a PDSCH,in slot n, and receives the value of K0 expressed by K0=1>0, this mayindicate that the PDSCH is scheduled in slot n+1. A scenario in which adata channel is scheduled in a slot after a control channel, i.e., aslot offset value (K0, K2) is larger than 0, may be referred to as“cross-slot scheduling”.

If the terminal has previously identified that a data channel is to becross-slot-scheduled, the terminal may perform an additional powerconsumption reducing operation. For example, the terminal may reducepower consumption by performing at least one of the following powerconsumption reduction operations.

-   -   in a slot in which a PDCCH is received, during a time interval        for which the PDCCH is decoded, the terminal may not buffer a        symbol to which a PDSCH may be scheduled.    -   in a slot in which a PDCCH is received, after the reception of        the PDCCH, the terminal may operate in a sleep mode during a        remaining time interval. A sleep mode may indicate that the        terminal does not activate the function of all or a part of        terminal operation elements (e.g., a baseband operation or radio        frequency (RF) circuit) in order to reduce power consumption.    -   the terminal may decode a received PDCCH with lowered processing        speed.

In order to support cross-slot scheduling, a base station may configureall of the slot offset values (K0, K2) in time domain resourceallocation information (e.g., a table) of a data channel, which may beconfigured through higher layer signaling (e.g., an SIB or RRC), to belarger than 0 for the terminal. If time domain resource allocationinformation including all of the slot offset values larger than 0 isconfigured for the terminal by the base station, the terminal mayidentify that cross-slot scheduling is always performed, and thus theterminal may reduce power consumption by performing the above-describedpower consumption reduction operations.

Even if cross-slot scheduling of a data channel is configured (e.g., allof the slot offset values (K0, K2) in time domain resource allocationinformation are configured to be larger than 0, or the base stationnotifies the terminal that cross-slot scheduling is to be performed(e.g., the minimum slot offset value (K0, K2) which can be scheduled isconfigured to be larger than 0)), the terminal may be required toperform CSI measurement and reporting by an aperiodic CSI request, andthus fail to perform the above-described power consumption reductionoperations.

For example, if a PDCCH received in slot n triggers aperiodic CSIreporting, and the offset value of a CSI-RS is 0, the terminal shouldmeasure the CSI-RS transmitted in slot n having received the PDCCH. Theterminal should be able to receive the CSI-RS in the slot havingreceived the PDCCH, and is thus unable to perform the above-describedpower consumption reduction operations. Therefore, for the terminal toreduce power consumption, an offset value of a CSI-RS should beconfigured to be larger than 0.

In accordance with an aspect of the disclosure, a CSI-RS resourceconfiguring methods for power consumption reduction of the terminal areprovided below.

Method 1

If cross-slot scheduling of a data channel is configured (e.g., all ofthe slot offset values (K0, K2) in a time domain resource allocationtable are configured to be larger than 0, the base station notifies theterminal through a series of methods that cross-slot scheduling is to beperformed, or the minimum slot offset value (K0, K2) which can bescheduled is configured to be larger than 0), the terminal may notexpect that aperiodic CSI reporting of a CSI-RS with an offset value of0 is triggered.

Alternatively, the terminal may not expect that the offset values of allthe CSI-RS resource sets for aperiodic CSI reporting are configured tobe 0.

The application of Method 1 may be limited to frequency range 2.

Method 2

If cross-slot scheduling of a data channel is configured (e.g., all theslot offset values (K0, K2) in a time domain resource allocation tableare configured to be larger than 0, the base station notifies theterminal through a series of methods that cross-slot scheduling is to beperformed, or the minimum slot offset value (K0, K2) which can bescheduled is configured to be larger than 0), the terminal may notexpect that aperiodic CSI reporting of a CSI-RS with an offset value of0 is triggered in a different slot, except for a slot in which a PDSCHis scheduled. That is, if a PDSCH is scheduled in a slot n, the terminalmay expect that aperiodic CSI reporting of a CSI-RS with an offset of 0may be triggered in slot n. On the contrary, if a PDSCH is not scheduledin a slot n for the terminal, the terminal may not expect that aperiodicCSI reporting of a CSI-RS with an offset of 0 may be triggered in slotn.

The application of Method 2 may be limited to frequency range 1.

Alternatively, the application of Method 2 may be limited to a casewhere if all the CSI-RSs in a CSI trigger state are not configured in aQCL-TypeD (i.e., a higher layer parameter qcl-Type is not configured tobe “QCL-TypeD”), an offset value of a CSI-RS as described above is fixedto 0.

Method 3

If cross-slot scheduling of a data channel is configured, the terminalmay expect that aperiodic CSI reporting is to be triggered only withrespect to a CSI-RS having a gap equal to or greater than a particularsymbol interval, between a last symbol of a PDCCH and a first symbol ofthe CSI-RS.

Alternatively, all of the CSI-RS resources for aperiodic CSI reportingmay be configured to ensure a gap greater than or equal to a particularsymbol interval, between a last symbol of a PDCCH and a first symbol ofa CSI-RS.

FIGS. 12 and 13 illustrate a transceiver, a memory, and a processor of aterminal and a base station to perform the embodiments above,respectively. The disclosure provides a CSI measurement and reportingmethod corresponding to the above embodiments and a method fortransmission or reception between a base station and a terminal forapplication of a data transmission or reception operation according tothe above method. Further, a transceiver, a memory, and a processor of aterminal and a base station should operate to perform the methodsaccording to embodiments, respectively.

FIG. 12 illustrates a terminal according to an embodiment.

Referring to FIG. 12 , a terminal includes a transceiver 1201, a memory1202, and a processor 1203. Alternatively, the terminal may include moreor less elements than illustrated in FIG. 12 . In addition, thetransceiver 1201, the memory 1202, and the processor 1203 may beimplemented into a single chip.

The transceiver 1201 may transmit a signal to a base station, or receivea signal from the base station. The signal may include controlinformation and data. The transceiver 1201 may include an RF transmitterthat up-converts and amplifies a frequency of a transmitted signal, anRF receiver that low-noise amplifies a received signal and down-convertsthe frequency, etc. In addition, the transceiver 1201 may receive asignal through a wireless channel and output the signal to the processor1203, and may transmit a signal output from the processor 1203, througha wireless channel.

The memory 1202 may store a program and data required for an operationof the terminal. In addition, the memory 1202 may store controlinformation or data included in a signal transmitted or received by theterminal. The memory 1202 may be configured by a storage medium such asa read only memory (ROM), a random access memory (RAM), a hard disk, acompact disc ROM (CD-ROM), and a digital versatile disc (DVD), or acombination of these and/or other storage mediums. In addition, thememory 1202 may be configured by a plurality of memories. The memory1202 may store a program for a CSI measurement/reporting method of theterminal, and a data transmission/reception operation according to themethod.

The processor 1203 may control a series of processes in which theterminal may operate according to embodiments described above. Forexample, the processor 1203 may differently control a CSImeasurement/reporting method of the terminal according to embodiments,and a data transmission/reception operation according to the method. Inaddition, the processor 1203 may include a plurality of processors, anddifferently control a CSI measurement/reporting method of the terminalaccording to embodiments, and a data transmission/reception operationaccording to the method by executing the program stored in the memory1202.

FIG. 13 illustrates a base station according to an embodiment.

Referring to FIG. 13 , a base station includes a transceiver 1301, amemory 1302, and a processor 1303. Alternatively, a base station mayinclude more or less elements than illustrated in FIG. 13 . In addition,the transceiver 1301, the memory 1302, and the processor 1303 may beimplemented into a single chip.

The transceiver 1301 may transmit a signal to a terminal, or receive asignal from the terminal. The signal may include control information anddata. The transceiver 1301 may include an RF transmitter thatup-converts and amplifies a frequency of a transmitted signal, an RFreceiver that low-noise amplifies a received signal and down-convertsthe frequency, etc. In addition, the transceiver 1301 may receive asignal through a wireless channel and output the signal to the processor1303, and may transmit a signal output from the processor 1303, througha wireless channel.

The memory 1302 may store a program and data required for an operationof a terminal. In addition, the memory 1302 may store controlinformation or data included in a signal transmitted or received by aterminal. The memory 1302 may be configured by a storage medium such asa ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination ofthese and/or other storage mediums. In addition, the memory 1302 mayinclude a plurality of memories. The memory 1302 may store a program fora CSI configuration/triggering method of the base station, and a datatransmission/reception operation according to the method.

The processor 1303 may control a series of processes so that the basestation can operate according to embodiments described above. Forexample, the processor 1303 may differently control a CSIconfiguration/triggering method of the base station according toembodiments, and a data transmission/reception operation according tothe method. In addition, the processor 1303 may include a plurality ofprocessors, and differently control a CSI configuration/triggeringmethod of the base station according to embodiments, and a datatransmission/reception operation according to the method by executingthe program stored in the memory 1302.

In the above-described embodiments of the disclosure, an elementincluded expressed in the singular or the plural according to presentedembodiment is not limited by to the singular or the plural. Instead, anelement expressed in the plural may also include a single element or anelement expressed in the singular may also include multiple elements.

The embodiments of the disclosure described and shown in thespecification and the drawings have been presented to easily explain thetechnical contents of the disclosure and help understanding of thedisclosure, and are not intended to limit the scope of the disclosure.As will be apparent to those skilled in the art, other modifications andchanges may be made thereto based on the technical spirit of thedisclosure. Further, the above respective embodiments may be employed incombination, as necessary. For example, the embodiments of thedisclosure may be partially combined to operate a base station and aterminal. The embodiments of the disclosure may be applied to othercommunication systems, and other variants based on the technical idea ofthe embodiments may be implemented.

In a wireless communication system in which a BWP is configured andoperated according to the above-described embodiments, if an activatedBWP is changed, a channel state of a changed BWP is effectively measuredand reported, and data can be more efficiently transmitted or receivedin the changed BWP, thereby reducing power consumption of a terminal.

While the disclosure has been shown and described with reference tocertain preferred embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the disclosure asdefined by the appended claims and any equivalents thereof.

What is claimed is:
 1. A method performed by a terminal in a wirelesscommunication system, the method comprising: receiving, from a basestation, information configuring a list of aperiodic trigger states forchannel state information (CSI); and receiving, from the base station,downlink control information (DCI) including a CSI request field,wherein a codepoint of the CSI request field is associated with onetrigger state of the list, and wherein the one trigger state comprisesat least one CSI report configuration, a CSI report configurationcomprises a CSI resource configuration, and the CSI resourceconfiguration comprises a bandwidth part (BWP) identifier (ID), whereinin case that a CSI report for a non-active BWP is triggered based on theCSI request field, a measurement based on a CSI resource in thenon-active BWP is not performed.
 2. The method of claim 1, wherein theCSI report configuration further comprises a serving cell index.
 3. Themethod of claim 1, wherein the information configuring the list isreceived based on a radio resource control (RRC) signaling.
 4. Themethod of claim 1, wherein in case that the BWP ID in the CSI resourceconfiguration identified by the codepoint of the CSI request field isdifferent from a BWP ID of an active BWP, a BWP corresponding to the BWPID in the CSI resource configuration is the non-active BWP.
 5. Themethod of claim 1, further comprising: in case that a CSI report for anactive BWP is triggered based on the CSI request field, performing ameasurement based on a CSI resource in the active BWP.
 6. A methodperformed by a base station in a wireless communication system, themethod comprising: transmitting, to a terminal, information configuringa list of aperiodic trigger states for channel state information (CSI);and transmitting, to the terminal, downlink control information (DCI)including a CSI request field, wherein a codepoint of the CSI requestfield is associated with one trigger state of the list, wherein the onetrigger state comprises at least one CSI report configuration, a CSIreport configuration comprises a CSI resource configuration, and the CSIresource configuration comprises a bandwidth part (BWP) identifier (ID),and wherein in case that a CSI report for a non-active BWP is triggeredbased on the CSI request field, a measurement based on a CSI resource inthe non-active BWP is not performed.
 7. The method of claim 6, whereinthe CSI report configuration further comprises a serving cell index. 8.The method of claim 6, wherein the information configuring the list istransmitted via a radio resource control (RRC) signaling.
 9. The methodof claim 6, wherein in case that the BWP ID in the CSI resourceconfiguration identified by the codepoint of the CSI request field isdifferent from a BWP ID of an active BWP, a BWP corresponding to the BWPID in the CSI resource configuration is the non-active BWP.
 10. Themethod of claim 6, further comprising: in case that a CSI report for anactive BWP is triggered based on the CSI request field, receiving, fromthe terminal, CSI associated with a measurement based on a CSI resourcein the active BWP.
 11. A terminal in a wireless communication system,the terminal comprising: a transceiver; and a processor configured to:receive, from a base station, information configuring a list ofaperiodic trigger states for channel state information (CSI), andreceive, from the base station, downlink control information (DCI)including a CSI request field, wherein a codepoint of the CSI requestfield is associated with one trigger state of the list, and wherein theone trigger state comprises at least one CSI report configuration, a CSIreport configuration comprises a CSI resource configuration, and the CSIresource configuration comprises a bandwidth part (BWP) identifier (ID),wherein in case that a CSI report for a non-active BWP is triggeredbased on the CSI request field, a measurement based on a CSI resource inthe non-active BWP is not performed.
 12. The terminal of claim 11,wherein the CSI report configuration further comprises a serving cellindex.
 13. The terminal of claim 11, wherein the information configuringthe list is received based on a radio resource control (RRC) signaling.14. The terminal of claim 11, wherein in case that the BWP ID in the CSIresource configuration identified by the codepoint of the CSI requestfield is different from a BWP ID of an active BWP, a BWP correspondingto the BWP ID in the CSI resource configuration is the non-active BWP.15. The terminal of claim 11, wherein the processor is furtherconfigured to: in case that a CSI report for an active BWP is triggeredbased on the CSI request field, perform a measurement based on a CSIresource in the active BWP.
 16. A base station in a wirelesscommunication system, the base station comprising: a transceiver; and aprocessor configured to: transmit, to a terminal, informationconfiguring a list of aperiodic trigger states for channel stateinformation (CSI), and transmit, to the terminal, downlink controlinformation (DCI) including a CSI request field, wherein a codepoint ofthe CSI request field is associated with one trigger state of the list,wherein the one trigger state comprises at least one CSI reportconfiguration, a CSI report configuration comprises a CSI resourceconfiguration, and the CSI resource configuration comprises a bandwidthpart (BWP) identifier (ID), and wherein in case that a CSI report for anon-active BWP is triggered based on the CSI request field, ameasurement based on a CSI resource in the non-active BWP is notperformed.
 17. The base station of claim 16, wherein the CSI reportconfiguration further comprises a serving cell index.
 18. The basestation of claim 16, wherein the information configuring the list istransmitted via a radio resource control (RRC) signaling.
 19. The basestation of claim 16, wherein in case that the BWP ID in the CSI resourceconfiguration identified by the codepoint of the CSI request field isdifferent from a BWP ID of an active BWP, a BWP corresponding to the BWPID in the CSI resource configuration is the non-active BWP.
 20. The basestation of claim 16, wherein the processor is further configured to, incase that a CSI report for an active BWP is triggered based on the CSIrequest field, receive, from the terminal, CSI associated with ameasurement based on a CSI resource in the active BWP.